From framework-dev
Use this skill to create and maintain blueprint files across all 6 phases of framework development. Provides templates, naming conventions, and directory structure guidance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/framework-dev:blueprint-generationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides templates and guidance for creating the comprehensive blueprint files that document project architecture, decisions, and implementation plans.
This skill provides templates and guidance for creating the comprehensive blueprint files that document project architecture, decisions, and implementation plans.
Initialize this structure at project start:
.framework-blueprints/
├── 00-project-state.json # Master state (see state-schema.json)
├── 01-discovery/
│ ├── outline-v1.md # Initial high-level outline
│ ├── outline-detailed.md # Expanded bullet points
│ ├── architecture-diagram.md # Mermaid + ASCII diagrams
│ ├── decisions-log.md # Decisions with sources
│ ├── premise-challenge.md # Premise validation
│ ├── dream-state.md # Current → Plan → 12-month ideal
│ └── alternatives.md # Implementation approaches considered
├── 02-structure/
│ ├── module-hierarchy.md # Complete module breakdown
│ ├── dependency-graph.md # Module relationships (ASCII + Mermaid)
│ ├── risk-assessment.md # Risks with confidence scores
│ ├── verbal-links.md # Connections in plain language
│ └── interaction-states.md # Loading/empty/error/success/partial table
├── 03-api-planning/
│ ├── api-contracts.md # All endpoints, schemas (SOURCE OF TRUTH)
│ ├── call-signs.md # Verified module connections
│ ├── coding-sequence.md # Task order with dependencies
│ └── scope-challenge.md # Complexity/search/completeness checks
├── 04-agent-assignment/
│ ├── work-division.md # How work is split
│ ├── llm-capabilities.md # Research on each LLM
│ ├── assignment-matrix.md # Which LLM → which tasks
│ └── prompts/ # Tailored prompts for each agent
├── 05-execution/
│ ├── handoff-protocol.md # Standard handoff format
│ ├── progress-tracker.md # Status dashboard
│ ├── shared-context.md # Context all agents need
│ ├── test-coverage-diagram.md # ASCII coverage map with gap analysis
│ ├── state-summary-phase-5.md # 50% checkpoint summary
│ └── handoffs/ # Individual handoff files
├── 06-integration/
│ ├── integration-checklist.md # All verification checks
│ ├── conflict-resolution.md # Conflicts and resolutions
│ ├── test-plan.md # Integration tests
│ ├── final-report.md # Complete project documentation
│ └── review-report.md # Findings summary with deferred items
└── backups/ # State file backups
Initialize per the canonical schema at skills/project-state-management/references/state-schema.json (single source of truth for all field definitions).
Templates are in templates/ directory:
templates/outline-template.md — Project outline structuretemplates/handoff-template.md — Agent handoff documenttemplates/progress-tracker-template.md — Execution dashboardtemplates/api-contract-template.md — API endpoint specificationFor decisions-log, api-contracts, and final-report: generate from the patterns above using project-specific data. Do not copy example data — populate from actual Phase 1-6 outputs.
| Type | Pattern | Example |
|---|---|---|
| Outline | outline-v{N}.md | outline-v1.md |
| State summary | state-summary-phase-{N}.md | state-summary-phase-5.md |
| Handoff | HO-{NNN}-{from}-to-{to}.md | HO-001-backend-to-frontend.md |
| Agent prompt | {role}-agent.md | backend-agent.md |
| Type | Pattern | Example |
|---|---|---|
| Decision | D{NNN} | D001 |
| Handoff | HO-{NNN} | HO-001 |
| Risk | R{NNN} | R001 |
| Task | T-{NNN} | T-001 |
graph TD
A[Module A] --> B[Module B]
A --> C[Module C]
B --> D[(Database)]
flowchart LR
User --> |Request| API
API --> |Query| DB[(Database)]
DB --> |Data| API
API --> |Response| User
sequenceDiagram
Client->>API: POST /login
API->>Auth: Validate
Auth-->>API: Token
API-->>Client: 200 OK
00-project-state.jsonnpx claudepluginhub ankurjain1121/framework-developer-agentCreates or updates technical blueprint documentation for features, APIs, and architecture. Searches existing blueprints first via Glob/Grep to avoid duplication, using standard structure and frontmatter.
Generates project-specific behavioral rules and commands from PRDs for Blueprint Development methodology, covering architecture patterns, testing strategies, implementation guides, and quality standards.
Generates persistent implementation blueprint with per-file specs: classifies work, scans code graph, confirms scope, analyzes impact, evaluates approaches. Use before features or refactors.