From blueprintflow
Part of the Blueprintflow methodology. Use when brainstorm has converged stances, a product-shape source of truth is needed, or a new blueprint module chapter is starting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/blueprintflow:bf-blueprint-writeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`docs/blueprint/*.md` = source of truth for product shape. Every later PR cites a §X.Y anchor here. Once frozen, execution follows the blueprint.
docs/blueprint/*.md = source of truth for product shape. Every later PR cites a §X.Y anchor here. Once frozen, execution follows the blueprint.
If bf-workflow is not active, STOP here. Load bf-workflow with the user's input; do nothing else in this skill until it routes back.
| File | Content |
|---|---|
README.md | Core stance list (10-15 stances, most authoritative) |
concept-model.md | First-class concepts + relationships |
<module>.md | Product shape per module (e.g. admin-model, channel-model, auth-permissions) |
onboarding-journey.md | User's first-time journey |
# <Module Name> (product shape)
## §1 Core concepts
### §1.1 <concept>
One-sentence definition + relationship to other concepts + constraint (X is, Y isn't).
## §2 Invariants / red lines
5-10 product-level red lines no execution can violate.
## §3 v0/v1 boundary
- v0 (no external users): free to drop DB / swap protocols
- v1 (first external user): forward-only schema / backups / gradual rollout
## §4 Constraints (kept for v2+)
What is explicitly not in v1's scope.
## §5 Acceptance hooks
How this connects to acceptance template / stance checklist (with anchors).
Each stance = one sentence + constraint + key scenario.
Validity test: if you can't write "X is, Y isn't" for a stance, it's not a stance — it's a platitude.
Every stance must produce 5-7 reverse-check items (used by bf-milestone-fourpiece stance checklist).
| Step | Action |
|---|---|
| 1. Concept discussion | Paired with bf-brainstorm. Lock 1-2 concepts/stances per round |
| 2. Write blueprint PR | Architect + PM write docs/blueprint/<module>.md. Dev + QA review too — stances must be accepted by all roles |
| 3. Core stance list | Distill 10-15 core stances into README.md, mark ⭐ important ones |
| 4. Blueprint freeze | Post-freeze changes require PR + four-role review. Reasons in changelog, affected milestones rechecked |
follow skill bf-blueprint-write
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub codetreker/blueprintflow --plugin blueprintflow