plan-feature

Name: plan-feature
Author: gtrabanco

35installs2forks

How to install plan-feature?

gtrabanco/agentic-workflow/plan-feature

$npx -y skills add gtrabanco/agentic-workflow --skill plan-feature

Installs into the current project.

Summary

Engineering-planning router for an already-designed feature. Given a feature whose SPEC product half is not marked designed, STOPS and redirects to /design-feature <slug> — no bypass flag. Given a designed feature, a GitHub issue #N (issue → scoped product half, satisfying ca

Files · 1

View on GitHub

SKILL.md

1	# Plan Feature (router)
2
3	The engineering-planning door for a feature whose product definition already
4	exists. Routes to a focused internal step so only the work you need runs (no
5	fat single skill). Docs only — no code, no branch. Product definition
6	(raw-idea interview, capability closure) is `design-feature`'s job, not this
7	one — see the redirect gate below.
8
9	## Turn contract — verify before ending the turn
10
11	```
12	✓ The redirect gate ran FIRST, before any SPEC edit: undesigned input → STOP,
13	print the fixed `/design-feature <slug>` block, do nothing else this turn
14	✓ Designed input only: engineering half filled, artifacts written, and the
15	roadmap entry registered (number, order, deps verified)
16	✓ If `plan-feature-scaffold` ran this turn: the roadmap row was re-read
17	AFTER the write and literally reads `planned` — a dropped `defined→planned`
18	write fails this box; do not end the turn until it's fixed
19	✓ The dependency & blocker check was RUN and its result decides which closing block is printed
20	✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
21	✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
22	```
23
24	About to end the turn with any box unchecked? The turn is NOT done — complete
25	the missing box first (weak models drop end-of-document duties; this list is
26	first on purpose).
27
28	## Step 0 — Discover the project (always first)
29
30	Per the agent guide's Workflow conventions + documentation map, then read
31	what THIS skill needs: the roadmap (`docs/features/ROADMAP.md`), so routing
32	and roadmap registration match the project's real layout.
33
34	## Redirect gate (always, before routing)
35
36	Before any other step, resolve the target slug/issue and read **the roadmap
37	status** (`docs/features/ROADMAP.md` → the five-state machine
38	`idea/defined/planned/in-progress/done`) — the primary gate signal. The
39	SPEC's `## Design status` marker is the SPEC-local record and the
40	legacy-compat fallback only (see step 6 below), never the primary check:
41
42	1. Roadmap row status `defined` → proceed to Routing below (the product
43	half is designed; the engineering half still needs scaffolding).
44	2. Roadmap row status `planned` (SPEC + artifacts already present) →
45	STOP. Never invoke `plan-feature-scaffold` — re-scaffolding an
46	already-planned feature is the re-plan-loop bug this gate exists to close.
47	Print exactly:
48
49	```
50	→ Next: /execute-phase <NN> P1 — this feature is already planned; start
51	implementation, don't re-plan it.
52	```
53	3. Roadmap row status `in-progress` → STOP. Print exactly:
54
55	```
56	→ Next: /execute-phase <NN> <next-phase> — this feature is already being
57	implemented; resume the current phase, don't re-plan it.
58	```
59	4. Roadmap row status `done` → STOP. Print exactly:
60
61	```
62	→ Next: nothing — <NN>-<slug> already shipped (roadmap status `done`).
63	```
64	5. Roadmap row status `idea`, or no row at all → STOP. Print exactly:
65
66	```
67	→ Next: /design-feature <slug> — this feature has no completed product design yet
68	(capability closure not done). Design it first; then re-run /plan-feature <slug>.
69	```
70
71	No bypass flag exists for this gate — an undesigned feature is never
72	planned by this skill, under any flag or instruction.
73	6. Legacy compat. A roadmap row still reading a plain `planned` with no
74	five-state history (predates this repo's roadmap-status-machine feature):
75	fall back to the SPEC marker — `## Design status: designed` and Capability
76	closure filled → treat as `defined`+`planned`, STOP

People who liked this also viewed

6 picks

Type

plan-feature

35installs2forks

View on GitHub

How to install plan-feature?

gtrabanco/agentic-workflow/plan-feature

$npx -y skills add gtrabanco/agentic-workflow --skill plan-feature

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Plan Feature (router)
2
3	The engineering-planning door for a feature whose product definition already
4	exists. Routes to a focused internal step so only the work you need runs (no
5	fat single skill). Docs only — no code, no branch. Product definition
6	(raw-idea interview, capability closure) is `design-feature`'s job, not this
7	one — see the redirect gate below.
8
9	## Turn contract — verify before ending the turn
10
11	```
12	✓ The redirect gate ran FIRST, before any SPEC edit: undesigned input → STOP,
13	print the fixed `/design-feature <slug>` block, do nothing else this turn
14	✓ Designed input only: engineering half filled, artifacts written, and the
15	roadmap entry registered (number, order, deps verified)
16	✓ If `plan-feature-scaffold` ran this turn: the roadmap row was re-read
17	AFTER the write and literally reads `planned` — a dropped `defined→planned`
18	write fails this box; do not end the turn until it's fixed
19	✓ The dependency & blocker check was RUN and its result decides which closing block is printed
20	✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
21	✓ The closing `→ Next:` block is printed as the ABSOLUTE last output
22	```
23
24	About to end the turn with any box unchecked? The turn is NOT done — complete
25	the missing box first (weak models drop end-of-document duties; this list is
26	first on purpose).
27
28	## Step 0 — Discover the project (always first)
29
30	Per the agent guide's Workflow conventions + documentation map, then read
31	what THIS skill needs: the roadmap (`docs/features/ROADMAP.md`), so routing
32	and roadmap registration match the project's real layout.
33
34	## Redirect gate (always, before routing)
35
36	Before any other step, resolve the target slug/issue and read **the roadmap
37	status** (`docs/features/ROADMAP.md` → the five-state machine
38	`idea/defined/planned/in-progress/done`) — the primary gate signal. The
39	SPEC's `## Design status` marker is the SPEC-local record and the
40	legacy-compat fallback only (see step 6 below), never the primary check:
41
42	1. Roadmap row status `defined` → proceed to Routing below (the product
43	half is designed; the engineering half still needs scaffolding).
44	2. Roadmap row status `planned` (SPEC + artifacts already present) →
45	STOP. Never invoke `plan-feature-scaffold` — re-scaffolding an
46	already-planned feature is the re-plan-loop bug this gate exists to close.
47	Print exactly:
48
49	```
50	→ Next: /execute-phase <NN> P1 — this feature is already planned; start
51	implementation, don't re-plan it.
52	```
53	3. Roadmap row status `in-progress` → STOP. Print exactly:
54
55	```
56	→ Next: /execute-phase <NN> <next-phase> — this feature is already being
57	implemented; resume the current phase, don't re-plan it.
58	```
59	4. Roadmap row status `done` → STOP. Print exactly:
60
61	```
62	→ Next: nothing — <NN>-<slug> already shipped (roadmap status `done`).
63	```
64	5. Roadmap row status `idea`, or no row at all → STOP. Print exactly:
65
66	```
67	→ Next: /design-feature <slug> — this feature has no completed product design yet
68	(capability closure not done). Design it first; then re-run /plan-feature <slug>.
69	```
70
71	No bypass flag exists for this gate — an undesigned feature is never
72	planned by this skill, under any flag or instruction.
73	6. Legacy compat. A roadmap row still reading a plain `planned` with no
74	five-state history (predates this repo's roadmap-status-machine feature):
75	fall back to the SPEC marker — `## Design status: designed` and Capability
76	closure filled → treat as `defined`+`planned`, STOP

People who liked this also viewed

6 picks

Type