← ClaudeAtlas

blueprint-developmentlisted

Generate project-specific rules from PRDs for Blueprint Development. Use when generating architecture, testing, or quality rules from requirements documents.
laurigates/claude-plugins · ★ 37 · Testing & QA · score 80
Install: claude install-skill laurigates/claude-plugins
# /blueprint:development Guide and reference for the Blueprint Development methodology that generates project-specific behavioral rules and workflow commands from PRDs (Product Requirements Documents). ## When to Use This Skill | Use this skill when... | Use alternative when... | |------------------------|-------------------------| | Starting Blueprint Development in a project | Project is already using Blueprint (use `/blueprint:status`) | | Need to generate rules from PRDs | Starting a brand new project with no PRD yet | | Want project-specific behavioral guidelines | Using generic development practices | | Creating workflow automation for a project | Working on isolated tasks without project context | For detailed rule templates, command templates, and generation guidelines, see [REFERENCE.md](REFERENCE.md). ## Context - Blueprint initialized: !`find docs/blueprint -maxdepth 1 -name 'manifest.json' -type f` - PRDs present: !`find docs/prds -name "*.md" -type f` - Rules directory: !`find .claude -maxdepth 1 -name 'rules' -type d` - Existing rules: !`find .claude/rules -maxdepth 1 -name "*.md"` - Project type: !`find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \) -type f -print -quit` ## Execution Execute the complete Blueprint Development setup and rule generation workflow: ### Step 1: Verify project readiness Check context values above: 1. If Blueprint initialized = "NO" → Error: "Blueprint not initiali