Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

sdd-new-phase

Append a new active phase to specs/roadmap.md. Parses existing phases (active and ✅-completed) to compute the next stable phase number per the lifecycle rule, grounds the proposal against specs/mission.md and specs/tech-stack.md, groups structured questions (goal, dependencies, priority) via AskUserQuestion, then collects a freeform bullet list for the phase body. Edits specs/roadmap.md in place, then invokes the built-in /review skill against the pending change before stopping — committing, pushing, and opening a PR are left to the user. Does not create a feature spec; that is /sdd-new-spec's job.

jentic · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add jentic/jentic-api-scorecard --skill sdd-new-phase

About this skill


name: sdd-new-phase description: Append a new active phase to specs/roadmap.md. Parses existing phases (active and ✅-completed) to compute the next stable phase number per the lifecycle rule, grounds the proposal against specs/mission.md and specs/tech-stack.md, groups structured questions (goal, dependencies, priority) via AskUserQuestion, then collects a freeform bullet list for the phase body. Edits specs/roadmap.md in place, then invokes the built-in /review skill against the pending change before stopping — committing, pushing, and opening a PR are left to the user. Does not create a feature spec; that is /sdd-new-spec's job. argument-hint: "[short title or one-sentence intent] (optional)" metadata: internal: true

/sdd-new-phase — add a new active phase to the roadmap

You are operating within a Spec-Driven Development (SDD) workflow. See .claude/rules/sdd-constitution.md.

The constitution (mission / tech-stack / roadmap) already exists in specs/. This skill adds a fresh active phase — a shippable, independently reviewable, testable vertical slice of work — to specs/roadmap.md as a new ## Phase N — Title block. After writing the edit it invokes the built-in /review skill against the pending change, then stops. Branching, committing, and opening a PR are user actions. Once the roadmap change is merged, /sdd-new-spec <N> materializes the phase into a feature spec.

Inputs

Argument in $ARGUMENTS (optional):

  • empty → prompt the user for a one-sentence description of the phase
  • short title or one-sentence intent → used as the starting point for title + goal derivation

Hard constraints

  • Roadmap-only — zero code changes, zero git actions. This skill never modifies anything outside specs/roadmap.md. It does not run git, gh, or any commit / branch / push / PR commands. The user handles git themselves after reviewing the edit.
  • Do not renumber existing phases. Phase numbers are stable identifiers; completed phases stay in the file with a ✅ marker on their heading (per the lifecycle rule in specs/roadmap.md). The new phase number is always max(all existing phase numbers) + 1 — count both active and ✅-completed phases.
  • Do not create a feature spec. That is /sdd-new-spec's job.
  • Do not touch the ## Later Phases (Not Yet Planned) section or the trailing <!-- Only include items here if they are clearly out of current scope. --> comment. Active phases and the parking lot are distinct.
  • Do not write to disk before AskUserQuestion completes. The structured questions lock in decisions that shape the entry; writing early wastes the call.
  • Ground the phase against specs/mission.md and specs/tech-stack.md. If the proposal obviously conflicts with the constitution (outside mission scope, violates a tech-stack invariant), stop and surface the conflict before asking the user to lock decisions.
  • Depends on: must reference real active phases. If the user names a dependency, it must match a current ## Phase N — Title in specs/roadmap.md (case-insensitive contains match is fine). Typos get corrected; invented names get rejected.

Phase 0 — Load context

Load in parallel:

  • @specs/mission.md
  • @specs/tech-stack.md
  • @specs/roadmap.md
  • @specs/lessons.md
  • @.claude/rules/sdd-constitution.md

No git state checks — this skill doesn't touch git.

After loading, scan specs/lessons.md for any lessons that apply to the proposed phase. Carry the relevant ones into Phase 2 (use them to shape AskUserQuestion options where appropriate) and Phase 4 (apply them when writing the phase body). Mention in Phase 6 which lessons influenced the entry. The lessons file is operational, not load-bearing: a lesson that does not apply to this phase is fine to skip — do not force-fit guidance.

Phase 1 — Parse roadmap, propose phase identity

Parse specs/roadmap.md to extract:

  • Every phase block (## Phase N — Title, with or without a trailing ✅): number, title, goal, Depends on:, Priority:, and a completed flag set when the heading ends with ✅. Ignore the ## Later Phases (Not Yet Planned) section.
  • Active phases are those without ✅; completed phases are those with ✅. The duplicate-overlap check below runs against active phases only — overlapping with already-shipped work is not a conflict.
  • Next phase number: max(all phase numbers, active and completed) + 1. Phase numbers never get reused, so completed phases count toward the ceiling.

If $ARGUMENTS is empty, prompt the user for a one-sentence description of what the phase delivers.

Duplicate-overlap check: if the proposal obviously overlaps with an existing active phase (strong keyword overlap with a phase title or goal), surface the overlap to the user and ask whether to proceed anyway, merge into the existing phase, or cancel. Do not silently proceed past an apparent duplicate.

Constitution-conflict check: reason briefly about whether the proposal fits within the project's mission scope and tech-stack invariants. If there is an obvious conflict (proposes a capability outside the mission; proposes a runtime dependency the tech-stack forbids; violates a load-bearing constraint named in specs/tech-stack.md), surface it and pause. If there is no obvious conflict, proceed silently — do not pad the response with "nothing conflicts" noise.

Derive a candidate title in Title Case (e.g. "Local Service Routing", not "local service routing" or "LOCAL SERVICE ROUTING"). Show it to the user alongside the proposed phase number and confirm (or let them override) before Phase 2.

Phase 2 — AskUserQuestion (MANDATORY, before any disk write)

Issue a single AskUserQuestion call containing three grouped questions. Each question offers 3–5 concrete options plus a freeform "other" write-in.

Question 1 — Goal (shapes the **Goal:** line):

  • Prompt: "One-sentence goal for this phase — what does shipping it mean?"
  • Optio
Read the complete source ↗