build
starsforks
How to install build?
parcadei/continuous-claude-v3/build
$npx -y skills add parcadei/Continuous-Claude-v3 --skill buildWorkflow orchestrator that chains existing skills for feature development
SKILL.md
| 1 | # Build - Workflow Orchestrator |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## Invocation |
| 6 | |
| 7 | ``` |
| 8 | /build <mode> [options] [description] |
| 9 | ``` |
| 10 | |
| 11 | ## Question Flow (No Arguments) |
| 12 | |
| 13 | 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. |
| 14 | |
| 15 | ### Phase 0: Workflow Selection |
| 16 | |
| 17 | ```yaml |
| 18 | question: "What would you like to do?" |
| 19 | header: "Workflow" |
| 20 | options: |
| 21 | - label: "Help me choose (Recommended)" |
| 22 | description: "I'll ask a few questions to pick the right workflow" |
| 23 | - label: "Greenfield - new feature" |
| 24 | description: "Chain: discovery → plan → validate → implement → commit → PR" |
| 25 | - label: "Brownfield - existing code" |
| 26 | description: "Chain: onboard → research → plan → validate → implement" |
| 27 | - label: "TDD - test-first" |
| 28 | description: "Chain: plan → test-driven-development → implement" |
| 29 | - label: "Refactor - improve structure" |
| 30 | description: "Chain: impact analysis → plan → TDD → implement" |
| 31 | ``` |
| 32 | |
| 33 | **Mapping:** |
| 34 | - "Help me choose" → Continue to Phase 1-4 questions |
| 35 | - "Greenfield" → Set mode=greenfield, skip to Phase 5 (description) |
| 36 | - "Brownfield" → Set mode=brownfield, skip to Phase 5 (description) |
| 37 | - "TDD" → Set mode=tdd, skip to Phase 5 (description) |
| 38 | - "Refactor" → Set mode=refactor, skip to Phase 5 (description) |
| 39 | |
| 40 | **If Answer is Unclear (via "Other"):** |
| 41 | ```yaml |
| 42 | question: "I want to understand your workflow needs. Did you mean..." |
| 43 | header: "Clarify" |
| 44 | options: |
| 45 | - label: "Help me choose" |
| 46 | description: "Not sure which workflow - guide me through questions" |
| 47 | - label: "Greenfield - new feature" |
| 48 | description: "Building something new with no existing code" |
| 49 | - label: "Brownfield - existing code" |
| 50 | description: "Adding to or modifying existing codebase" |
| 51 | - label: "Neither - let me explain differently" |
| 52 | description: "I'll describe what I'm trying to do" |
| 53 | ``` |
| 54 | |
| 55 | ### Phase 1: Project Context |
| 56 | |
| 57 | ```yaml |
| 58 | question: "Is this a new feature or work in existing code?" |
| 59 | header: "Context" |
| 60 | options: |
| 61 | - label: "New feature from scratch" |
| 62 | description: "No existing code to integrate with" |
| 63 | - label: "Adding to existing codebase" |
| 64 | description: "Need to understand current code first" |
| 65 | - label: "Refactoring existing code" |
| 66 | description: "Improving without changing behavior" |
| 67 | ``` |
| 68 | |
| 69 | **Mapping:** |
| 70 | - "New feature from scratch" → greenfield mode |
| 71 | - "Adding to existing codebase" → brownfield mode |
| 72 | - "Refactoring existing code" → refactor mode |
| 73 | |
| 74 | **If Answer is Unclear (via "Other"):** |
| 75 | ```yaml |
| 76 | question: "I want to make sure I understand. Did you mean..." |
| 77 | header: "Clarify" |
| 78 | options: |
| 79 | - label: "New feature from scratch" |
| 80 | description: "Building something new with no existing code" |
| 81 | - label: "Adding to existing codebase" |
| 82 | description: "Integrating with code that already exists" |
| 83 | - label: "Refactoring existing code" |
| 84 | description: "Improving structure without changing behavior" |
| 85 | - label: "Neither - let me explain differently" |
| 86 | description: "I'll provide more details" |
| 87 | ``` |
| 88 | |
| 89 | ### Phase 2: Requirements Clarity |
| 90 | |
| 91 | ```yaml |
| 92 | question: "How clear are your requirements?" |
| 93 | header: "Requirements" |
| 94 | options: |
| 95 | - label: "I have a clear spec/description" |
| 96 | description: "Know exactly what to build" |
| 97 | - label: "I have a rough idea" |
| 98 | description: "Need help fleshing out details" |
| 99 | - label: "Just exploring possibilities" |
| 100 | description: "Want to discover what's possible" |
| 101 | ``` |
| 102 | |
| 103 | **Mapping:** |
| 104 | - "Clear spec" → --skip-discovery |
| 105 | - "Rough idea" → run discovery-interview first |
| 106 | - "Exploring" → run discovery-interview with broader scope |
| 107 | |
| 108 | **If Answer is Unclear (via "Other"):** |
| 109 | ```yaml |
| 110 | question: "I want to make sure I understand your requirements state. Did you mean..." |
| 111 | header: "Clarify" |
| 112 | options: |
| 113 | - label: "I have a clear spec/description" |
| 114 | description: "Ready to implement - no discovery needed" |
| 115 | - label: "I have a rough idea" |
| 116 | description: "Need some help defining the details" |
| 117 | - label: "Just exploring possibilities" |
| 118 | description: "Don't know exactly what's possible yet" |
| 119 | - label: "Neither - let me explain differently" |
| 120 | description: "I'll describe my situation better" |
| 121 | ``` |
| 122 | |
| 123 | ### Phase 3: Development Approach |
| 124 | |
| 125 | ```yaml |
| 126 | question: "How should I approach development?" |
| 127 | header: "Approach" |
| 128 | options: |
| 129 | - label: "Just implement it" |
| 130 | description: "Standard implementation flow" |
| 131 | - label: "Write tests first (TDD)" |
| 132 | description: "Test-driven development" |
| 133 | - label: "Validate plan before coding" |
| 134 | description: "Get plan reviewed before implementation" |
| 135 | ``` |
| 136 | |
| 137 | **Mapping:** |
| 138 | - "Just implement" → standard chain |
| 139 | - "Tests first" → tdd mode (overrides previous if not refac |
People who liked this also viewed
6 picksType
- lark-openapi-explorer飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。SkillsJul 2026
- lark-skill-maker创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill（包装原子 API 或编排多步流程）时使用。SkillsJul 2026
- azure-cost-optimizationOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
- vercel-react-native-skillsVercel's official collection of agent skillsSkillsJul 2026
- mcp-builderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate externaSkillsJul 2026
- gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.SkillsJul 2026
