From composure
Generates persistent implementation blueprint with per-file specs: classifies work, scans code graph, confirms scope, analyzes impact, evaluates approaches. Use before features or refactors.
How this skill is triggered — by the user, by Claude, or both
Slash command
/composure:blueprintThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured "think before building" step — from requirements discovery through implementation planning. Like building a house: the architect surveys the land and gathers requirements (Phase 0), then draws the blueprint with structural specs (Phase 1). One skill, two phases.
Structured "think before building" step — from requirements discovery through implementation planning. Like building a house: the architect surveys the land and gathers requirements (Phase 0), then draws the blueprint with structural specs (Phase 1). One skill, two phases.
Load each step through the fetch command (handles caching, decryption, and auth):
"~/.composure/bin/composure-fetch.mjs" skill composure blueprint {step-filename}
Do NOT read cache files directly — they are encrypted at rest. Always use the fetch command above.
| # | File |
|---|---|
| 1 | 00a-preflight.md |
| 2 | 00b-intent-analysis.md |
| 3 | 00c-ecosystem-research.md |
| 4 | 00d-stack-options.md |
| 5 | 00e-requirements-confirm.md |
| 6 | 00f-scaffold.md |
| 7 | 00g-auto-initialize.md |
| 8 | 01-classify.md |
| 9 | 02-graph-scan.md |
| 10 | 03-impact-analysis.md |
| 11 | 04a-load-docs.md |
| 12 | 04b-write-blueprint.md |
| 13 | 04c-handoff.md |
00c-ecosystem-research.md00d-stack-options.md00e-requirements-summary.md04b-blueprint-document.mdnpx claudepluginhub hrconsultnj/claude-plugins --plugin composureGenerates step-by-step implementation plans from design specs for multi-step tasks, verifying APIs and dependencies exist before coding, detailing files, code, tests, commits.
Creates graph-informed implementation plans by scanning codebase, analyzing blast radius, and producing machine-readable task breakdowns before writing code.
Plans and architects new features by analyzing requirements, asking clarifying questions, and creating a detailed implementation plan aligned with project architecture. Invoke before coding begins.