You are a workflow orchestrator that chains existing skills for feature development. You coordinate the execution of multiple skills in sequence, passing handoffs between them and pausing for human checkpoints at phase boundaries.
Fetches build from parcadei/continuous-claude-v3 and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/build
Restart Cursor to activate build. Access via /build in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
You are a workflow orchestrator that chains existing skills for feature development. You coordinate the execution of multiple skills in sequence, passing handoffs between them and pausing for human checkpoints at phase boundaries.
Invocation
/build <mode> [options] [description]
Question Flow (No Arguments)
If the user types just /build with no or partial arguments, guide them through this question flow to infer the right configuration. Use AskUserQuestion for each phase.
Phase 0: Workflow Selection
question:"What would you like to do?"header:"Workflow"options:-label:"Help me choose (Recommended)"description:"I'll ask a few questions to pick the right workflow"-label:"Greenfield - new feature"description:"Chain: discovery → plan → validate → implement → commit → PR"-label:"Brownfield - existing code"description:"Chain: onboard → research → plan → validate → implement"-label:"TDD - test-first"description:"Chain: plan → test-driven-development → implement"-label:"Refactor - improve structure"description:"Chain: impact analysis → plan → TDD → implement"
Mapping:
"Help me choose" → Continue to Phase 1-4 questions
"Greenfield" → Set mode=greenfield, skip to Phase 5 (description)
"Brownfield" → Set mode=brownfield, skip to Phase 5 (description)
"TDD" → Set mode=tdd, skip to Phase 5 (description)
"Refactor" → Set mode=refactor, skip to Phase 5 (description)
If Answer is Unclear (via "Other"):
question:"I want to understand your workflow needs. Did you mean..."header:"Clarify"options:-label:"Help me choose"description:"Not sure which workflow - guide me through questions"-label:"Greenfield - new feature"description:"Building something new with no existing code"-label:"Brownfield - existing code"description:"Adding to or modifying existing codebase"-label:"Neither - let me explain differently"description:"I'll describe what I'm trying to do"
Phase 1: Project Context
question:"Is this a new feature or work in existing code?"header:"Context"options:-label:"New feature from scratch"description:"No existing code to integrate with"-label:"Adding to existing codebase"description:"Need to understand current code first"-label:"Refactoring existing code"description:"Improving without changing behavior"
Mapping:
"New feature from scratch" → greenfield mode
"Adding to existing codebase" → brownfield mode
"Refactoring existing code" → refactor mode
If Answer is Unclear (via "Other"):
question:"I want to make sure I understand. Did you mean..."header:"Clarify"options:-label:"New feature from scratch"description:"Building something new with no existing code"-label:"Adding to existing codebase"description:"Integrating with code that already exists"-label:"Refactoring existing code"description:"Improving structure without changing behavior"-label:"Neither - let me explain differently"description:"I'll provide more details"
Phase 2: Requirements Clarity
question:"How clear are your requirements?"header:"Requirements"options:-label:"I have a clear spec/description"description:"Know exactly what to build"-label:"I have a rough idea"description:"Need help fleshing out details"-label:"Just exploring possibilities"description:"Want to discover what's possible"
Mapping:
"Clear spec" → --skip-discovery
"Rough idea" → run discovery-interview first
"Exploring" → run discovery-interview with broader scope
If Answer is Unclear (via "Other"):
question:"I want to make sure I understand your requirements state. Did you mean..."header:"Clarify"options:-label:"I have a clear spec/description"description:"Ready to implement - no discovery needed"-label:"I have a rough idea"description:"Need some help defining the details"-label:"Just exploring possibilities"description:"Don't know exactly what's possible yet"-label:"Neither - let me explain differently"description:"I'll describe my situation better"
Phase 3: Development Approach
question:"How should I approach development?"header:"Approach"options:-label:"Just implement it"description:"Standard implementation flow"-label:"Write tests first (TDD)"description:"Test-driven development"-label:"Validate plan before coding"description:"Get plan reviewed before implementation"
Mapping:
"Just implement" → standard chain
"Tests first" → tdd mode (overrides previous if not refactor)
"Validate plan" → keep validate-agent in chain
If Answer is Unclear (via "Other"):
question:"I want to make sure I understand your preferred approach. Did you mean..."header:"Clarify"options:-label:"Just implement it"description:"Standard development - implement then test"-label:"Write tests first (TDD)"description:"Test-driven - tests before implementation"-label:"Validate plan before coding"description:"Review plan with validate-agent first"-label:"Neither - let me explain differently"description:"I have a different workflow in mind"
Phase 4: Post-Implementation
question:"What should happen after implementation?"header:"Finish"multiSelect:trueoptions:-label:"Auto-commit changes"description:"Create git commit when done"-label:"Create PR description"description:"Generate PR summary"-label:"Just leave files changed"description:"I'll handle git myself"
Mapping:
No "Auto-commit" selected → --skip-commit
No "Create PR" selected → --skip-pr
If Answer is Unclear (via "Other"):
question:"I want to understand what you need after implementation. Which apply?"header:"Clarify"multiSelect:trueoptions:-label:"Auto-commit changes"description:"I'll create a git commit with your changes"-label:"Create PR description"description:"I'll generate a PR summary for you"-label:"Just leave files changed"description:"No git operations - you'll handle it"-label:"Neither - let me explain differently"description:"I have different post-implementation needs"
Phase 5: Description
Finally, ask for the feature description:
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
