---
name: sdd-manage
description: Coordinate complete release-message preparation, Git release highlights, release package/workflow preparation and GitHub releases alongside SDD workflows for initial development, feature preparation, bounded or resumed task implementation, human-directed checkpoint amendments, accepted feature integration, focused review or maintenance, and hosted task synchronization. Use for multi-stage project requests, shared prerequisites, branch management and phase transitions, workflow transitions, stopping boundaries, recovering shell authentication, or supplying hosting credentials to sdd-forge.
---

# Coordinate specification-driven development

For Markdown output or document work within this skill's scope, apply the shared [Markdown style](../sdd-conventions/references/markdown-style.md): blank lines after headings and around top-level lists and code blocks, plus four-space structural indentation, including nested lists, with exactly one space after each list marker. This applies to direct calls as well as coordinated work; it does not expand editing or review authority.

Translate the user's objective into a scoped workflow and coordinate the responsible skills. Proactively identify relevant capabilities, prerequisites, missing decisions, coordination gaps and blockers at entry, preparation handoff, phase activation and completion. Act on routine authorized work; raise consequential unresolved choices before dependent work and preserve the requested stopping boundary. Use the request and established session decisions as authorization; continue routine steps within that scope without repeated confirmation. Reviewer assessment ends at its report commit; publication remains part of the complete workflow under existing scope. Host automatic review is a separate platform control, not a plugin review skill. Discussion, assessment, or review alone does not authorize edits. Start at the requested stage when its inputs are established, and stop at the requested boundary. Apply [human document review](references/human-document-review.md): broad workflow authority does not preaccept newly created documents; acceptable existing inputs permit normal continuation after startup assessment.

| Coordination concern | Load |
| --- | --- |
| Select a practical workflow and its entry, outputs, and stopping point | [available workflows](references/workflows.md) |
| Create/maintain root AGENTS.md without weakening governing instructions | [agent orientation](references/agent-orientation.md) |
| Start greenfield exploration and place disclosure/usage records in the first target-repository SDD commit | [repository bootstrap](references/repository-bootstrap.md) |
| Select human review at entry and pause after each necessary new document | [human document review](references/human-document-review.md) |
| Enforce SPEC/PLAN/TASKS preparation readiness and affected reassessment | [document QC gates](references/document-qc-gates.md) |
| Establish prerequisites, pass scope, resolve blockers, and persist results | [coordination protocol](references/coordination.md) |
| Resolve identities, create/reuse workflow branches, or manage phase transitions | [branch management](references/branch-management.md) |
| Publish each workflow-owned commit before advancing or making another commit | [per-commit publication](references/git-workflows.md#publish-each-commit) |
| Integrate verified boundaries or continue a blocked merge | [Git workflows](references/git-workflows.md) |
| Discover, save, or supply a repository token; recover shell/API authentication | [hosting credentials](references/credentials.md) |
| Establish optional GitHub tracking recommendation, confirmation and retained scope | [tracking decision](references/tracking-decision.md) |
| Gate phase eligibility and active hosted object creation before execution | [phase activation](references/phase-activation.md) |
| Run an explicitly selected comprehensive prerelease review, or issue its advisory release reminder | [prerelease review](references/prerelease-review.md) |
| Open a nested revision or amend the eligible last closed campaign | [revision modes](references/revision-modes.md) |
| Plan or coordinate focused/systematic review and accepted revisions | [review and revision](references/review-and-revision.md) |
| Prepare complete release messages, local Git highlights, release packages/workflows or create/finish a GitHub release | [release operations](references/workflows.md#release-operations) and sdd-forge's [complete release messages](../sdd-forge/references/release-message.md), [shared Git highlights](../sdd-forge/references/release-highlights.md) or selected [GitHub backend](../sdd-forge/references/github.md) |
| Check representative requests and expected boundaries | [workflow examples](references/examples.md) |

1. **Establish the request.** Identify the project, objective, requested operation, authoritative inputs, and stopping boundary. Distinguish initial preparation, feature deltas, task-list implementation, checkpoint steering, integration, and focused review. Ask only for missing decisions that materially prevent the requested work.
2. **Orient at startup.** Invoke **sdd-orient** for a current scoped handoff: project and Git roots, governing instructions, documents, environment, branch and HEAD, dirty-path ownership, and interrupted task state. At greenfield entry, load [repository bootstrap](references/repository-bootstrap.md#greenfield-startup) before exploration or the first persistence operation. Read-only discussion can proceed outside Git; repository mutations require an eligible worktree. Re-orient when material state or scope changes.
3. **Coordinate the responsible skills.** Before an implementation handoff, load [tracking decision](references/tracking-decision.md) and [phase activation](references/phase-activation.md). An explicit tracking request is confirmation even when no objects exist; required pending/unknown projection blocks task execution. Carry the actual decision and verified phase objects/associations or concrete blocker through the handoff. Follow the selected workflow. Supply the objective, allowed paths and effects, authoritative decisions, task IDs where applicable, Git baseline, pending-change ownership, and exit conditions. Load their instructions rather than reproducing their procedures. Commit project preparation on design-docs; before creating a dependent implementation branch, explicitly merge, verify and publish accepted preparation into the actual default branch under the branch-management gate. Campaign plans/reports belong on the campaign revision branch. Preserve valid existing work; dirty state alone does not justify reset.
4. **Respect ownership and decisions.** Leave executable range selection, main execution, completion, commits, and pushes to **sdd-implement**, and checkpoint amendments to **sdd-steer**. Leave accepted feature reconciliation to **sdd-integrate-feature**. Return governing-document amendments identified by **sdd-docs** to the user; do not automatically route them into authoring. Proactively establish the [tracking decision](references/tracking-decision.md); coordinate hosted writes only when confirmed/requested or already active for the selected scope.
5. **Finish and stop.** Coordinate explicit integration/publication only when the workflow's integration gate is met: main development requires full phase completion; a partial task/milestone range pushes and pauses on its phase branch. Collect evidence and unresolved differences. For authorized repository changes outside implementation or steering, coordinate scoped verification, commit composition through **sdd-report**, commit, and push as specified by the request and project policy. Report blockers accurately. Never resume implementation after steering without a separate human instruction.

For task-list execution, enforce the [task commit contract](../sdd-implement/references/completion-and-checkpoints.md#task-commit-contract) at handoff and completion: exactly one executable task closes per commit, its result/evidence and initial owning checkbox are together, and its subject starts with exactly one owning `[<task-id>]` marker. Do not permit cumulative task closure or detached initial status commits. Require the bounded [persistence audit](../sdd-implement/references/completion-and-checkpoints.md#task-persistence-audit-and-recovery) on continuation and before applicable integration; resolve reported violations within explicit recovery authority rather than silently rewriting history. Non-task campaign/preparation and merge work retains its own formats.

Apply [per-commit publication](references/git-workflows.md#publish-each-commit) across all coordinated work and direct focused calls. Publish/read back every workflow-owned commit before advancing or making another commit; an unresolved push blocks progression. Do not batch local commits for later publication. Explicit user-directed local-only/deferred publication remains a scoped exception.

Use **sdd-report** for presentation, keeping planned, implemented, verified, committed, pushed, and hosted states distinct. Return the accomplished objective, affected artifacts or task IDs, evidence and limitations, commit/push and hosting outcomes when applicable, remaining decisions, and the exact stopping point. Do not require a transaction journal, recovery directory, extra issue map, or a new skill for interruption recovery. This coordinator requires the focused skills selected by the workflow; if one is unavailable, report the blocked capability rather than claiming it ran.

Apply [revision modes](references/revision-modes.md) before a nested campaign or selected closed-campaign amendment; verify amendment eligibility/authority rather than silently reopening. Respect the [closed campaign record boundary](../sdd-conventions/references/review-campaigns.md#closed-campaign-records): retain closed packages unchanged and outside routine context loading or current validation, except the selected package while explicitly reopened under that procedure. Consult them only for a specific current need; later changes create no historical-compatibility work or reporting obligation.