How this command is triggered — by the user, by Claude, or both
Slash command
/sigma:blueprintThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /blueprint Design the **system architecture** for the chosen approach. ## Behavior 1. Read `proposals.md` and the chosen approach. 2. Produce `architecture.md` covering: - Components and their single responsibilities - Data flow (sources → transforms → sinks; for ML: data → features → model → serving) - Interfaces between components (well-defined boundaries) - Key decisions and their rationale - Risks and mitigations - Which `sigma` domains own which components 3. Favor small, isolated, independently-testable units. ## Rules - Each unit: what it does, how it's used,...
Design the system architecture for the chosen approach.
proposals.md and the chosen approach.architecture.md covering:
sigma domains own which components→ /grill --target blueprint (catch design/logic flaws before spec) → /spec
npx claudepluginhub navidgh66/sigma --plugin sigma/blueprintGenerates an execution-ready implementation plan from a specification, including system architecture design, component interfaces, and dependency-ordered task breakdown. Supports --input and --component flags for customization.
/blueprintTransforms feature descriptions, bug reports, or improvement ideas into structured project blueprints via multi-phase workflow with discovery, research, and architecture.
/blueprintGenerates or updates a Verso blueprint document from Lean source files, producing per-declaration mathematical statements, proof sketches, and an interactive dependency graph. Also supports single-file and single-declaration sub-targets.