plan

Name: plan
Author: owainlewis

238stars46forks

How to install plan?

owainlewis/blueprint/plan

$npx -y skills add owainlewis/blueprint --skill plan

Installs into the current project.

Summary

Breaks a reviewed design or brief into ordered, agent-ready tasks, tickets, and optional milestones. Use when the user asks to break a feature or project into implementation tasks, create implementation tickets or issues from a design, brief, or project, define milestones, or pre

Files · 1

View on GitHub

SKILL.md

1	# Plan
2
3	## Workflow
4
5	1. Read the source, repository instructions, and relevant code.
6	2. Stop and return to design if product or technical choices remain open.
7	3. Break the work into vertical, outcome-based tasks small enough for one agent run. Order them by dependency. Add milestones only when they create a useful delivery or review boundary.
8	4. Return the plan in chat by default. Create tracker tickets only when the user asks. Never write a plan document.
9	5. Stop after planning. Do not implement.
10
11	Each task must stand alone:
12
13	```markdown
14	## <Task title>
15
16	### Outcome
17	The working result.
18
19	### Context
20	What a new agent needs with no session history.
21
22	### Constraints
23	Decisions and behavior that must not change.
24
25	### Acceptance criteria
26	- Testable condition.
27
28	### Checks
29	Exact commands and any required manual verification.
30
31	### Out of scope
32	Related work this task must not absorb.
33	```
34
35	## Boundaries
36
37	- Do not split by file or technical layer when one vertical slice can deliver working behavior.
38	- Do not create scaffolding or cleanup tasks without a checked outcome.
39	- Do not hide unresolved decisions inside implementation tickets.

People who liked this also viewed

6 picks

Type

plan

238stars46forks

View on GitHub

How to install plan?

owainlewis/blueprint/plan

$npx -y skills add owainlewis/blueprint --skill plan

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Plan
2
3	## Workflow
4
5	1. Read the source, repository instructions, and relevant code.
6	2. Stop and return to design if product or technical choices remain open.
7	3. Break the work into vertical, outcome-based tasks small enough for one agent run. Order them by dependency. Add milestones only when they create a useful delivery or review boundary.
8	4. Return the plan in chat by default. Create tracker tickets only when the user asks. Never write a plan document.
9	5. Stop after planning. Do not implement.
10
11	Each task must stand alone:
12
13	```markdown
14	## <Task title>
15
16	### Outcome
17	The working result.
18
19	### Context
20	What a new agent needs with no session history.
21
22	### Constraints
23	Decisions and behavior that must not change.
24
25	### Acceptance criteria
26	- Testable condition.
27
28	### Checks
29	Exact commands and any required manual verification.
30
31	### Out of scope
32	Related work this task must not absorb.
33	```
34
35	## Boundaries
36
37	- Do not split by file or technical layer when one vertical slice can deliver working behavior.
38	- Do not create scaffolding or cleanup tasks without a checked outcome.
39	- Do not hide unresolved decisions inside implementation tickets.

People who liked this also viewed

6 picks

Type