blueprint

jeremytondo's avatarfrom jeremytondo

Standardized workflow for managing technical blueprints in the .blueprints/ directory.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The Blueprint Skill provides a standardized, automated workflow for managing technical blueprints within a dedicated directory. It streamlines the entire software development lifecycle—from initial idea capture and architectural planning to execution and final review—ensuring that all technical decisions are documented, immutable, and consistently followed by AI agents to maintain project integrity.

Use Cases

  • Architectural Planning: Use the skill to architect complex systems and document technical strategies before implementation begins, ensuring a solid foundation for development.
  • Technical Project Lifecycle Management: Track the progress of technical tasks through structured phases (capture, planning, executing, completed) with automated checklist updates and status tracking.
  • Standardized Documentation: Maintain a single source of truth for technical specifications in the .blueprints/ directory, ensuring team-wide alignment and preventing unauthorized direct edits to core blueprints.
  • Quality Assurance and Review: Integrate a mandatory review process into the development workflow to ensure that implementations strictly adhere to the original architectural blueprint.
nameblueprint
descriptionStandardized workflow for managing technical blueprints in the .blueprints/ directory.

Blueprint Skill

Use this skill when the user explicitly requests a "Blueprint" workflow (e.g., via /blueprint).

Workflow Rules

  1. Source of Truth: All formal blueprints live in the .blueprints/ directory.
  2. Delegation: Do not edit .blueprints/ files directly. Always delegate to the @blueprint-manager subagent using the Task tool.
  3. Idea Integrity: The Idea section of a blueprint is immutable once the status moves past capture.
  4. Lifecycle:
    • capture: Use @blueprint-manager to record initial notes.
    • planning: Use the Plan agent to architect, then delegate to @blueprint-manager to document the strategy and execution steps.
    • executing: Use the Build agent to implement and delegate checklist updates to @blueprint-manager. Before completion, run /review to ensure quality.
    • completed: Use @blueprint-manager to finalize the implementation summary and record the review findings.

Session Protocol

Once this skill is loaded, you must proactively suggest using @blueprint-manager for any non-trivial tasks. Ensure all architectural decisions are documented before implementation begins.