How this command is triggered — by the user, by Claude, or both
Slash command
/workflow:build [object Object]The summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the `builder` agent defined in `agents/builder.md`. Load and follow the implementation workflow from `skills/execute-plan/SKILL.md`. Execute implementation in this order: 1. Read existing code — match patterns in the service 2. Entity changes (TypeORM) 3. Migration file — WRITE ONLY, never run 4. DTOs — class-validator, no `any` 5. Service methods — try/catch on all async 6. Controller — @UseGuards(JwtAuthGuard) 7. Module — register providers 8. Tests — 80%+ coverage --- The user's input for this session is: $ARGUMENTS
Invoke the builder agent defined in agents/builder.md.
Load and follow the implementation workflow from skills/execute-plan/SKILL.md.
Execute implementation in this order:
anyThe user's input for this session is:
$ARGUMENTS
npx claudepluginhub ramchanderpeddada/workflow-plugin --plugin workflow/buildExecutes incremental, test-driven implementation of tasks from a plan. Accepts "auto" to run through the entire plan without human stepping between tasks.
/buildBuilds, compiles, and packages projects with error handling, optimization for dev/prod/test, and detailed reporting. Supports optional target and flags like --type, --clean, --optimize.
/buildScaffolds a VitePress site from existing wiki markdown files, adding dark theme, dark-mode Mermaid diagrams, and click-to-zoom for images and diagrams.
/buildPlans and executes against SPEC.md with optional target selection, verification contracts, and auto-backprop on failure.
/buildBuilds a macOS/iOS Shortcut end-to-end via a delegate agent. Pass a natural-language brief describing the desired shortcut functionality.
/buildBuilds a task from a Notion page URL: fetches details and properties, implements per spec with progress updates in Notion, communicates via comments if needed, then marks complete with optional diff explanation.