dev-orchestrator

name	dev-orchestrator
description	Orchestrates systematic development workflow for any software development task - from simple bug fixes to complex multi-file features. Separates specification from implementation, provides testing guidance, and manages completion workflow. Use when user requests to implement, build, develop, or fix any code.

Orchestrates systematic workflow for all software development by separating specification from implementation Keeps main context clean for requirements gathering while implementation happens in focused, isolated sub-agent contexts User requests to implement, build, develop, or create new functionality User requests to fix bugs or issues Task requires any code changes (simple or complex) User wants systematic approach with testing guidance Task involves multiple files or architectural decisions Clarify requirements and generate structured spec Execute spec in clean sub-agent context User performs manual testing with provided guidance User confirms and feature is archived

<tool_restrictions> <allowed_tools> Invoke dev-spec and dev-execute skills Clarify requirements before specification </allowed_tools> <forbidden_tools> Do not spawn sub-agents directly - use dev-execute skill instead Do not read specifications - let dev-execute handle that Do not create specifications directly - use dev-spec skill instead </forbidden_tools> <orchestrator_role>This is a GUIDANCE skill that instructs Claude to invoke other skills at appropriate times</orchestrator_role> </tool_restrictions>

This is an ORCHESTRATOR skill - provide guidance and invoke dev-spec and dev-execute, do not implement directly Always use dev-spec to create specifications before implementation Always use dev-execute to execute specifications, never implement in main context Never archive features automatically - dev-execute handles two-phase workflow (implementation then user confirmation) After dev-execute completes implementation and provides testing steps, remind user to test before marking complete When user confirms "feature X is complete", invoke dev-execute in completion mode to archive For multiple related changes, discuss parallel vs sequential execution with user Adapt specification complexity to task complexity (dev-spec handles this) Features stay in ./.dev-docs/features/ until user confirms testing complete

<complete_workflow> <phase_1 name="specification"> dev-spec skill Clarify requirements with user through targeted questions Ask about architecture, patterns, constraints, success criteria Generate XML-structured specification with implementation guidance Save to ./.dev-docs/features/[number]-[name].md Ask user: "Ready to execute this specification?" dev-spec automatically adjusts depth based on task complexity </phase_1>

<phase_2 name="implementation"> User confirms ready to execute specification dev-execute skill Invoke dev-execute with feature number or name dev-execute reads specification from ./.dev-docs/features/ Spawns sub-agent in clean context with specification as prompt Sub-agent implements and provides suggested manual testing steps Feature remains in ./.dev-docs/features/ (NOT archived yet) <execution_strategies> One specification, focused implementation Multiple independent specs with no shared files Multiple dependent specs that must run in order </execution_strategies> </phase_2>

<phase_3 name="testing"> dev-execute completes implementation and provides testing steps Present testing suggestions from sub-agent to user Remind user: "Feature X has been implemented. Please test using the steps above, then confirm completion when ready." Wait for user to perform manual testing Feature stays in ./.dev-docs/features/ during testing Do NOT automatically archive or mark complete - wait for explicit user confirmation </phase_3>

<phase_4 name="completion"> User explicitly confirms: "feature X is complete", "archive feature X", "mark feature X done" Invoke dev-execute in completion mode dev-execute adds completion metadata and archives to ./.dev-docs/features/completed/ Confirm to user: "Feature X archived to completed/" </phase_4> </complete_workflow>

<integration_with_dev_feature> <two_phase_workflow> <what_happens>Sub-agent implements code and provides testing steps</what_happens> Feature stays in ./.dev-docs/features/ awaiting testing <no_automatic_archiving>Feature is implemented but not yet marked complete</no_automatic_archiving> User confirms testing complete <what_happens>dev-execute archives to ./.dev-docs/features/completed/</what_happens> Feature marked complete with metadata (executed timestamp, completed timestamp) </two_phase_workflow> <testing_phase_guidance> <after_implementation>Always remind user to test before marking complete</after_implementation> <testing_steps>Sub-agent provides specific, actionable testing steps</testing_steps> <user_control>User decides when testing is complete and feature is ready to archive</user_control> </testing_phase_guidance> <completion_triggers> feature X is complete archive feature X mark feature X done complete feature X </completion_triggers> </integration_with_dev_feature>

<skill_integration> feature-creator (this skill) - provides workflow guidance dev-spec - creates executable specifications dev-execute - implements specifications in sub-agents <communication_flow> User requests development work feature-creator invokes dev-spec dev-spec clarifies requirements and creates specification dev-spec saves to ./.dev-docs/features/ dev-spec asks user: "Execute now?" If yes, feature-creator invokes dev-execute dev-execute spawns sub-agent and implements Sub-agent provides testing steps, feature stays in ./.dev-docs/features/ feature-creator reminds user to test User tests and confirms: "feature X is complete" feature-creator invokes dev-execute in completion mode dev-execute archives to ./.dev-docs/features/completed/ </communication_flow> </skill_integration>

<complexity_handling> <simple_work> Bug fixes, single-file changes, small enhancements dev-spec generates lightweight specification Quick, focused implementation with minimal overhead </simple_work> <complex_work> Multi-file features, architectural changes, new components dev-spec generates comprehensive specification with extended thinking Thorough planning ensures quality implementation </complex_work> dev-spec automatically adjusts depth based on task complexity signals </complexity_handling>

Main context stays clean for requirements gathering and planning Implementation happens in fresh context with only the specification No pollution from exploration mixed with execution Systematic thinking produces comprehensive specifications Clear success criteria ensure completion signals Testing guidance built into every implementation Two-phase workflow prevents premature completion Specifications saved as reviewable markdown files Can edit and rerun specifications Archive completed work for reference Parallel execution for independent components Sequential execution for dependent tasks No token concerns with Claude Max

<error_handling> dev-spec cannot create specification Ask user for more details about requirements Retry specification with additional context

dev-execute reports implementation errors Feature stays in ./.dev-docs/features/ (not archived) Review error details with user May need to revise specification and re-execute User tests and finds problems Do not archive current feature Option 1: Create new specification for fixes and execute Option 2: Revise original specification and re-execute Archive only after user confirms everything works User wants to modify feature after seeing results Do not archive current feature Create new specification for modifications Execute modification specification User tests combined result, then confirms completion

<orchestrator_behavior> <automation_level> <when_invoked>Automatically invoke dev-spec for specification phase</when_invoked> <after_spec>Ask user if ready to execute, then invoke dev-execute if confirmed</after_spec> <after_implementation>Remind user to test, wait for confirmation before archiving</after_implementation> <on_completion_trigger>Invoke dev-execute in completion mode to archive</on_completion_trigger> </automation_level> <user_control> User can review/edit specification before execution User controls when to execute User controls testing timeline User explicitly confirms completion before archival </user_control> </orchestrator_behavior>

Fix the login button that's not responding on mobile feature-creator invokes dev-spec dev-spec asks: "What's the expected behavior? Any specific mobile devices affected?" Generates lightweight specification (simple fix) Saves to ./.dev-docs/features/001-fix-login-button.md User confirms: "Execute now" feature-creator invokes dev-execute Sub-agent fixes button, provides testing steps: "Test on iOS Safari and Android Chrome" Feature stays in ./.dev-docs/features/001-fix-login-button.md User tests on mobile devices Verifies button works correctly User confirms: "Feature 001 is complete" feature-creator invokes dev-execute in completion mode Feature archived to ./.dev-docs/features/completed/001-fix-login-button.md Build a user authentication system with OAuth support feature-creator invokes dev-spec dev-spec asks: "OAuth providers? Token storage? Session management?" Generates comprehensive specification with architecture details Saves to ./.dev-docs/features/002-user-authentication.md User confirms: "Execute now" feature-creator invokes dev-execute Sub-agent implements OAuth flow, provides detailed testing steps Feature stays in ./.dev-docs/features/002-user-authentication.md User tests OAuth flow with different providers Verifies token storage and session management Finds issue with token refresh User: "Token refresh isn't working" feature-creator invokes dev-spec for fix Creates 003-fix-token-refresh.md Executes fix, user tests again User confirms: "Features 002 and 003 are complete" feature-creator invokes dev-execute for both Both archived to ./.dev-docs/features/completed/ Build separate auth, API, and UI components in parallel feature-creator invokes dev-spec dev-spec creates 3 independent specifications Saves as 004-auth.md, 005-api.md, 006-ui.md User confirms: "Execute all in parallel" feature-creator invokes dev-execute: "Execute features 004, 005, 006 in parallel" dev-execute spawns 3 sub-agents simultaneously (one message) All 3 provide testing steps, remain in ./.dev-docs/features/ User tests auth component - works User tests API component - works User tests UI component - has bug User: "Features 004 and 005 are complete" feature-creator archives 004 and 005, leaves 006 for fixing Create 007-fix-ui-bug.md, execute, test User: "Features 006 and 007 are complete" Archive both to completed/ Set up database, create migrations, then seed data (must be in order) dev-spec creates 3 specifications in sequence 008-setup-database.md, 009-create-migrations.md, 010-seed-data.md User: "Execute sequentially" dev-execute executes 008, waits for completion, provides testing User tests database setup: "Feature 008 is complete" dev-execute archives 008, executes 009, provides testing User tests migrations: "Feature 009 is complete" dev-execute archives 009, executes 010, provides testing User tests seed data: "Feature 010 is complete" dev-execute archives 010 Sequential execution allows testing between dependent steps I need to add dark mode support to the app I'll orchestrate the development workflow. First, let me invoke dev-spec to create a specification. *invokes dev-spec* dev-spec is working on the specification... Specification created and saved to ./.dev-docs/features/011-dark-mode.md. Ready to execute? Yes *invokes dev-execute* Implementation complete! Suggested manual testing steps: 1. Toggle dark mode in settings 2. Verify all pages render correctly in dark mode 3. Check color contrast meets accessibility standards

    Feature 011 has been implemented. Please test using the steps above, then let me know when it's complete.</agent>
  <user>*user tests*</user>
  <user>Everything looks good. Feature 011 is complete.</user>
  <agent>*invokes dev-execute in completion mode*</agent>
  <agent>Feature 011 has been archived to ./.dev-docs/features/completed/011-dark-mode.md</agent>
</conversation>

<related_skills> Creates XML-structured feature specifications with adaptive complexity Executes specifications in sub-agents with two-phase testing workflow </related_skills>