sajor2000/methodsmith / plugins/methodsmith/skills/method-plan
method-plan
VerifiedCreates the durable plan for data-science work: an implementation plan or, for studies, a statistical analysis plan (SAP). Use when the user asks to plan work or write a SAP.
references/confidence-check.md
View on GitHub# Confidence Check (5.3.0-5.3.2)
Load this after the plan file is written (Phase 5.2), or when Phase 0.1 short-circuits an existing plan to Phase 5.3. It decides whether to deepen; `SKILL.md` names the files for the next steps.
## Deepening modes
- **Auto mode** (default during plan generation): runs without asking for approval. The user sees what is being strengthened; sub-agent findings are synthesized directly into the plan.
- **Interactive mode** (from the Phase 0.1 deepen fast path): the user explicitly asked to deepen. Present each sub-agent's findings for review; the user can accept, reject, or discuss them, and only accepted findings are synthesized.
Interactive mode applies whether the plan was generated by this skill, written by hand, or produced by another tool. The confidence check strengthens rationale, sequencing, risk treatment, and grounding; it does not replace `method-doc-review` (5.3.8), which checks clarity, completeness, and scope.
**Pipeline mode:** always auto mode in pipeline / `disable-model-invocation` contexts.
## 5.3.1 Classify Plan Depth and Topic Risk
Determine depth using the Phase 0.6 tiers (Lightweight 2-4 units, Standard 3-6, Deep 4-8 or phased delivery).
High-risk signals:
- Authentication, authorization, or security-sensitive behavior
- Payments, billing, or financial flows
- Data migrations, backfills, or persistent data changes
- External APIs or third-party integrations
- Privacy, compliance, or user data handling, including PHI, patient-level data, small-cell disclosure, or IRB/DUA constraints
- Reported statistical inference: primary endpoints, causal claims, multiplicity, or deviations from a SAP
- Cross-interface parity or multi-surface behavior
- Significant rollout, monitoring, or operational concerns
## 5.3.2 Gate: Decide Whether to Deepen
- **Lightweight** plans usually do not need deepening unless high-risk.
- **Standard** plans often benefit when one or more important sections still look thin.
- **Deep** or high-risk plans often benefit from a targeted second pass.
- **Thin local grounding override:** if Phase 1.2 triggered external research because local patterns were thin (fewer than 3 direct examples or an adjacent-domain match), always proceed to scoring.
Outcomes:
- **Sufficiently grounded and no override:** report "Confidence check passed — no sections need strengthening" and continue to 5.3.8 as directed in `SKILL.md`. Document review is still mandatory.
- **Deepening warranted:** continue to 5.3.3-5.3.7 as directed in `SKILL.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |