Plan feature scaffold
Skill gtrabanco/agentic-workflow/skills/plan-feature-scaffold
Internal step of plan-feature: from an already-designed SPEC (product half `designed`), fill the **engineering half** and generate the planning artifact set scaled to the feature's size (XS/S → SPEC-only with ≥ 2 phases in the SPEC, last = Hardening & PR; M/L → full set with a hardening phase), freeze one compact ACCEPTANCE.md for every size, and register the roadmap entry. Docs only — never code.From its SKILL.md
npx -y skills add gtrabanco/agentic-workflow --skill plan-feature-scaffoldAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.5 KB, as published. Nobody here has run it
Plan Feature — Scaffold (internal)
Turn a designed feature into the project's complete planning artifact set,
ready for phase-by-phase execution. Fills only the SPEC's engineering half
— the product half (goal, context, scope, capability closure) already exists
and is marked designed before this skill ever runs (plan-feature's
redirect gate guarantees it). Docs only — never code.
When to use
- The
plan-featurerouter calls this once a feature's product half isdesigned— fromdesign-feature,plan-feature-from-issue, or an already-scoped slug/SPEC — to fill the engineering half of itsdocs/features/<NN>-<slug>/SPEC.mdand the rest of the folder, then update the roadmap.
Not for product definition (that is design-feature) or writing code (that is
execute-phase) or deciding whether to build (that is the plan-feature
router / triage-issue).
Step 0 — Discover the project (always first)
Per the agent guide's Workflow conventions + documentation map, then read what THIS skill needs: the feature SPEC template, the roadmap (numbering/order/deps), 1–2 recent feature folders to mirror the artifact set, and the architecture/domain docs the map points to. No template/roadmap → fall back to the agent guide and state the assumption.
Progressive loading — scaffold only after discovery
The reference allowlist is exactly one path. After Step 0, read and execute the complete scaffold process. It owns the product- half gate, artifact scaling, roadmap transition, re-read, and fixed completion report. The phase contract owns the 8-box phase-lint and the normalized phase fingerprint.
The resource is normative and one hop from this file. Missing resource → stop; never reconstruct phase or close-out wording from memory.
The verification contract owns the
ACCEPTANCE.md schema, validation ladder, and anti-weakening rules. Consume it
after the engineering plan is complete and before registering planned.
Guardrails
- Docs only. No source edits, migrations, or dependencies.
- Respect the architecture: honor layer rules (inner layers don't import outer) and any domain/i18n/SEO/a11y rules from the docs map.
- Architectural invariants. The planning preflight
owns the normalized repository state read and the ONE final architectural
classification for the whole plan; consume it here. Its absence is compatible:
record
n/a: no project invariants declaredin the engineering half. For every applicable rule, record its ID, repository evidence, andpreserves | violates | introduces | changesclassification in### Architecture impact. Onlypreservesmay produce phases; the other classifications stop for an explicit architectural decision through the project's declared authority — and only after the full plan exists, never converted into a phase task or inferred from the product half. - Surface conflicts (numbering clashes, dependency cycles, scope overlap) before writing, not after.
- Otherwise honor the project's Workflow conventions (branch/PR, docs-language).
Relationship to other skills
Invoked by the plan-feature router (after design-feature /
plan-feature-from-issue designed the product half, or directly for an
already-designed scoped slug/SPEC). Hands off to execute-phase for P1;
audit-docs audits anytime.
Done when
docs/features/<NN>-<slug>/exists with the SPEC's engineering half +ACCEPTANCE.md+ every scaled planning artifact filled — the product half untouched from whatdesign-feature/plan-feature-from-issuewrote.- The roadmap lists the feature with correct number, order, dependencies, and
status
planned(thedefined → plannedwrite this skill owns) — re-read and confirmed after the write, not assumed from having run it. - No code changed; open questions captured in
decisions.md.
What ships with it: 1 file
3.9 KB alongside SKILL.md
references/
- SCAFFOLD_PROCESS.md3.9 KB
Gives 0 of the 12 instructions most project setup skills give
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- Discover the project first
- Fill only the engineering half
- Surface conflicts before writing
- Update the roadmap status to planned
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.