Convert user intent into a spec-driven workflow for code changes.
npx skills add https://github.com/curdx/curdx-flow --skill bmad-quick-dev-curdx
Please help me install this Agent Skill. Skill: bmad-quick-dev Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-quick-dev Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-quick-dev-curdx
This Skill converts ambiguous developer intent into a disciplined, spec-driven implementation plan that produces clean, working artifacts aligned with the repository’s architecture and conventions.
epic-<N>-context.md file to prevent context rot.Ask for a single focused code change (e.g., “Add browser-verified CRUD for todos in this repo”) and run the bmad-quick-dev workflow so it generates a reviewable spec, implements it, and prepares a structured review order.
High-intent search queries and answers about installing and using this skill.
Spec-driven code implementation converts ambiguous intent into actionable, logically ordered tasks using a clarify, plan, implement, review, and present workflow. It enforces Ready-for-Development standards with Given/When/Then testable criteria to produce clean working artifacts.
Epic context compilation prevents context rot by compiling only relevant developer context into an epic-N-context.md file. This maintains story continuity across sequential tasks, ensuring each implementation step aligns with the broader feature requirements.
Human-gated approval checkpoints halt automated workflow execution when intent or spec gaps appear. This ensures safe routing by pausing sequential step processing for clarification before proceeding to code implementation or review orchestration.
Yes, spec generation requires python3 and supports feature, bugfix, refactor, or tweak requests. It routes work safely through a disciplined loop, producing reviewable specs and structured review orders for any actionable code change.
Automated workflow processing halts at checkpoints when intent or spec gaps are detected. This guardrail ensures tasks meet Ready-for-Development standards, requiring human-gated decisions to resolve ambiguities before proceeding to implementation or review.
Placeholder-free acceptance criteria are needed whenever preparing tasks for Ready-for-Development standards. This ensures every generated task is actionable, logically ordered, and fully testable using Given/When/Then structures before implementation begins.
workinprogress-aiRoute development tasks to appropriate skills via structured questions and registry lookup.
riethmayerOrchestrate consensus planning with Planner, Architect, and Critic review cycles.
spallempatiEnforce Given/When/Then acceptance tests in release candidate CI pipelines.
xloxn69Generates a complete user story template with YAML frontmatter and markdown sections.