---

name: sdlc-develop description: Orchestrates 6-phase SDLC pipeline for feature development. Use when user runs /develop command, requests guided feature development, wants to create implementation plans, or mentions "develop", "feature", "implement", "plan feature", "SDLC", "spec-driven development". Supports plan persistence, resume mode, and autonomous execution.

SDLC Develop Skill

Lightweight orchestrator for 6-phase software development lifecycle with progressive disclosure.

Core Principles

• Phase 0 is MANDATORY - Always analyze existing implementations before designing new ones
• Search first, load on demand - Use Grep to find relevant sections before loading files
• Ask clarifying questions early - Identify ambiguities before designing, not after
• Use TodoWrite - Track all progress throughout every phase
• Load phases progressively - Only read phase files when entering that phase

Quick Start

Copy/develop add user authentication         # Full 6-phase pipeline
/develop add logout button --auto        # Autonomous mode
/develop create plan for dashboard --plan-only  # Plan only
/develop @arkhe/specs/01-user-auth/      # Resume existing plan

Arguments

Parse from $ARGUMENTS:

Mode Detection

VERIFY_MODE - If --verify-arch or --verify-impl flags present:

• Require @path reference to existing spec directory
• Load spec artifacts (spec.md, plan.md, tasks.md, api-contract.md if exists)
• Run verification workflow(s) based on flags:
  • --verify-arch → Read VERIFY-ARCH.md
  • --verify-impl → Read VERIFY-IMPL.md
  • Both flags → Run both verifications
• Output verification report using verification-report.md.template
• Does NOT execute SDLC phases

RESUME_MODE - If @path reference found AND plan.md exists (no verify flags):

• Read existing plan from path
• Ask user which phase to continue from
• Skip to that phase, load only that phase file

PLAN_MODE - If keywords "create plan", "plan for", "draft plan" OR --plan-only:

• Execute Phases 0-2 only
• Save spec.md and plan.md
• Stop with resume instructions

FULL_MODE - Default:

• Execute all 6 phases sequentially
• User checkpoints between phases (unless --auto)

Phase Routing

Load phase files only when entering that phase:

Model Tiers

Spec Directory Structure

Plans are persisted to arkhe/specs/ with auto-incrementing prefixes:

Copyarkhe/specs/
├── 01-user-auth/
│   ├── spec.md       # Requirements
│   ├── plan.md       # Architecture
│   └── tasks.md      # Task breakdown
├── 02-dashboard/
└── ...

Templates

Configuration

If .arkhe.yaml exists at project root:

Copydevelop:
  specs_dir: arkhe/specs  # Default
  numbering: true         # NN- prefix
  ticket_format: full     # full | simple

First run without config prompts for preferences.

Execution Flow

CopySTART
  │
  ├─ Parse arguments (flags, path references)
  ├─ Detect mode (RESUME/PLAN/FULL)
  │
  ├─ [RESUME] Load plan.md → Ask which phase → Jump to phase
  │
  ├─ [PLAN/FULL] Read PHASE-0-DISCOVERY.md
  │   └─ Execute Phase 0 → Checkpoint
  │
  ├─ Read PHASE-1-REQUIREMENTS.md
  │   └─ Execute Phase 1 → Checkpoint
  │
  ├─ Read PHASE-2-ARCHITECTURE.md
  │   └─ Execute Phase 2 → Save plan → [PLAN stops here]
  │
  ├─ [FULL] Read PHASE-3-WORKSTREAMS.md
  │   └─ Execute Phase 3 → Checkpoint
  │
  ├─ Read PHASE-4-IMPLEMENTATION.md
  │   └─ Execute Phase 4 → Validation
  │
  └─ Read PHASE-5-SUMMARY.md
      └─ Execute Phase 5 → Complete

Checkpoints (unless --auto)

User approval required at:

• End of Phase 0 (existing system findings)
• End of Phase 1 (requirements summary)
• Phase 2c (architecture decision)
• End of Phase 3 (task breakdown)
• Phase 4d (quality review findings)

Checkpoint Protocol (CRITICAL)

At every numbered prompt checkpoint:

1. STOP - Halt all execution immediately
2. PRESENT - Display the numbered prompt exactly as shown
3. WAIT - Do not take any further action until user responds
4. RESPOND - Act based on user's numbered choice:
   • 1 (APPROVE) - Proceed to next phase/step
   • 2 (REVIEW) - Show requested details, then re-present prompt
   • 3 (MODIFY/FIX) - Make changes, then re-present prompt
   • 4 (CANCEL) - Stop the pipeline entirely

Tier 1 Checkpoints (⛔ CANNOT SKIP)

These checkpoints block execution regardless of flags:

• Phase 2c: Architecture Decision
• Phase 4e: Completion Gate

YOU MUST STOP AND WAIT. Even with --auto, do not proceed until user explicitly responds.

Tier 2 Checkpoints (⚠️ RECOMMENDED)

Without --auto: STOP and WAIT for user response. With --auto: Auto-approve and proceed, logging the decision.

Gates (HITL Tiers)

Three-tier Human-in-the-Loop framework based on risk level:

Conditional Escalation: Any phase auto-elevates to Tier 1 if:

• Database schema changes detected
• Security implementation involved
• Breaking API changes proposed

See GATES.md for decision criteria and prompt patterns.

Examples

See EXAMPLES.md for detailed usage scenarios.

Troubleshooting

See TROUBLESHOOTING.md for common issues.