Individual skill

plan

Use when an approved, clarified spec must become a technical blueprint before any code — the SDD phase between clarify and tasks: architecture, contracts, data flow, testing strategy, sequencing and risks, at structure altitude, never framework syntax. NOT the what/why spec (that is `specify`), NOT the ambiguity sweep (that is `clarify`), NOT the task breakdown (that is `tasks`), NOT the code (that is `implement`).

skills/plan/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 561
Repository last updated: Nov 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agentic-ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
claude-code Repository topic
cli Repository topic
cline Repository topic
codex Repository topic
coding-assistant Repository topic
cursor Repository topic
sdd Declared skill tag
plan Declared skill tag
design Declared skill tag
design Derived category
engineering Derived category
data Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 10,094 bytes
evals/README.mddoc · 3,837 bytes
evals/cases.yamlasset · 5,434 bytes
references/plan-template.mddoc · 6,151 bytes

Read excerpt


# Plan — the technical blueprint between spec and tasks

The spec says **what** and **why**. `plan` decides **how**: the components, the contracts between
them, the data that flows, how each claim gets proven, and what is most likely to bite. It reads the
clarified spec and the constitution, writes ONE artifact — `02-DOCS/wiki/sdd/plans/<slug>.md` — and
hands off to `tasks`, which slices it into an ordered, independently-verifiable checklist.

```text
constitution → specify → clarify → [ plan ] → tasks → analyze → implement → verify → review → ship
```

## Decide structure, not syntax

A plan names components, contracts, shapes and flows. It does not write the framework's route