Produce a dependency graph, data flow, and interfaces before implementation.
npx skills add https://github.com/rockandrolla13/blueprint --skill design-rockandrolla13
Please help me install this Agent Skill. Skill: design Source: https://github.com/rockandrolla13/blueprint/tree/main/design Command: npx skills add https://github.com/rockandrolla13/blueprint --skill design-rockandrolla13
Structured architecture design phase that produces a dependency graph, data flow, interfaces, and a review checkpoint before any code is written. Use this skill when the user says "design", "architect", "structure", "plan the implementation", "how should I build this", or transitions from ideation to commitment — e.g., "ok let's go with approach X, design it". Also trigger when the user says "build", "implement", or "create" for anything that will span multiple files or modules — the skill enforces a design phase before implementation begins. Do NOT trigger for single-function tasks, bug fixes, or refactoring (those have their own skills). Do NOT trigger for open-ended exploration — that belongs to the ideate skill.
Describe the system architecture and interfaces before writing code.
High-intent search queries and answers about installing and using this skill.
Plan software architecture by defining a formal problem framing, identifying core abstractions, and enumerating components. This structured design phase produces a dependency graph, data flow, and documented interfaces to guide multi-file implementations before coding begins.
You need a structured architecture design phase when transitioning from ideation to commitment, or when building systems that span multiple files or modules. It enforces a review checkpoint to prevent scope creep and requires documented interfaces before implementation.
A software architecture plan for multi-file modules should include a dependency graph, data flow mapping, interface design, and component enumeration. It yields a structured handoff documenting architecture decisions to guide downstream teams during implementation.
No, this architecture design approach does not work for single-function tasks, bug fixes, or refactoring. It is specifically built for multi-file module planning and enforces a design checkpoint before implementation begins on larger system builds.
Prevent scope creep by enforcing a structured review checkpoint during the architecture design phase. This requires a defined problem framing, core abstractions, and documented interfaces before any implementation work proceeds downstream.
The best way to document architecture decisions is through a structured handoff that captures the formal problem framing, dependency graph, data flow, and interface design. This ensures downstream teams have clear guidance for multi-file implementations.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
Martingale42Translate research outputs into a NautilusTrader component architecture document.
cipherstashValidate code review feedback against the implementation plan to prevent scope creep.
gara2000Analyze open-ended topics and generate structured ideas in multi-round ideation.
