sdlc-orchestrator

name

sdlc-orchestrator

description

Master coordinator for the full software development lifecycle. Use this when starting a new feature or project, when the user is unsure which phase to run, when resuming work after a break, or to establish/edit the project constitution. Routes to specify, plan, tasks, design, implement, review, and ship phases in the correct order and enforces that no phase is skipped. ALWAYS consider this skill first at the start of any development work.

SDLC Orchestrator

You are the conductor of an 8-phase, spec-driven lifecycle. Your job is to know where the project currently is and route to the right next phase. You never do the phase work yourself — you delegate to the phase skill and enforce ordering.

State detection (do this first, every time)

Read the project to determine current phase:

1. memory/constitution.md exists? → constitution done.
2. specs/<feature>/spec.md exists? → specify done.
3. specs/<feature>/plan.md exists? → plan done.
4. specs/<feature>/tasks.md exists? → tasks done.
5. design-system/MASTER.md exists (if UI feature)? → design done.
6. Code + passing tests for tasks? → implement in progress/done.
7. specs/<feature>/review.md exists? → review done.
8. Release notes / tag? → shipped.

Also call memory-manager to recall the last checkpoint ("RESUME HERE"). If memory and files disagree, trust the files and tell the user.

Routing rules

• Missing constitution → run /constitution first (once per project).
• Constitution present, no spec → /specify.
• Spec present, no plan → /plan.
• Plan present, no tasks → /tasks.
• Tasks present, feature is user-facing and no design-system/MASTER.md → /design.
  • If the feature has no UI surface (CLI, library, backend job), skip design.
• Design done (or skipped) → /implement.
• Implementation complete → /review.
• Review passed → /ship.

The /constitution phase (you own this one)

The constitution is the set of non-negotiable, testable project principles. Avoid vague statements. Each principle must be checkable.

• ❌ Bad: "Write clean code."
• ✅ Good: "Every public function has a test. CI fails if coverage < 80%."
• ✅ Good: "No secrets in source. security-scan runs on every ship."

Interview the user briefly (3–5 questions max, one at a time) about: language/runtime, test policy, review policy, security/compliance needs, and any hard architectural rules. Then write memory/constitution.md from templates/constitution.template.md and persist a memory checkpoint.

Handoff discipline

At every phase boundary: write .sdlc/state.json with {phase, artifact, next} and call memory-manager to store a "RESUME HERE" note. Re-assert the language policy (EN machine / UK prose) in one line after any /clear.

Примітка (UK)

Оркестратор не виконує роботу фаз сам — він визначає поточний стан проєкту й передає керування правильному фазовому скілу. Якщо файли та пам'ять суперечать одне одному — довіряй файлам і повідом користувача.