Skip to content

sajor2000/methodsmith / plugins/methodsmith/skills/method-plan

method-plan

Verified

Creates 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/origin-document.md

View on GitHub
# Origin Document Intake (Phases 0.3 and 0.5)

Load this when Phase 0.2 found a relevant requirements document (unified artifact or legacy `docs/brainstorms/` requirements).

## 0.3 Use the Source Document as Primary Input

1. Read it thoroughly.
2. Announce that it will serve as the origin document for planning.
3. Carry forward:
   - Problem frame
   - Actors (A-IDs), Key Flows (F-IDs), and Acceptance Examples (AE-IDs) when present — constraints that implementation units must honor
   - Requirements and success criteria
   - Scope boundaries (including `Deferred for later` and `Outside this study's scope` subsections — or legacy `Outside this product's identity` — when present)
   - Key decisions and rationale
   - Dependencies or assumptions
   - Outstanding questions, preserving whether they are blocking or deferred
4. Use the source document as the primary input to planning and research.
5. Reference important carried-forward decisions with `(see origin: <source-path>)`.
6. Do not silently omit source content — if the origin discussed it, the plan must address it, even briefly. Before finalizing, scan each origin section to verify nothing was dropped.
7. When the source uses `artifact_contract: ce-unified-plan/v1`, preserve its Product Contract verbatim except for explicitly resolved corrections, add the Planning Contract and execution sections to the same file, and retain its path as the canonical plan path.

## 0.5 Classify Outstanding Questions Before Planning

If the origin contains `Resolve Before Planning` or similar blocking questions:

- Review each one.
- Reclassify it as planning-owned work **only if** it is a technical, architectural, or research question.
- Keep it as a blocker if it would change product behavior, scope, or success criteria.

If true product blockers remain, surface them and ask (one blocking question, numbered fallback) whether to:
1. Resume `method-brainstorm` to resolve them
2. Convert them into explicit assumptions or decisions and continue

Do not continue planning while true blockers remain unresolved.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall