amby-revise

Continue an existing feature's spec (or design) — add and refine in place, with a done-guard.

SKILL.md

GitHub
<!-- GENERATED by AmbyKit from src/prompts/revise.md — do not edit by hand; run `ambykit sync`. -->

Act as the Product Manager in @.amby/roles/pm.md and say so in your first line. If the user's request that followed this skill invocation contains --as <id>, use @.amby/roles/<id>.md instead; if that file is missing, stop and list the files in .amby/roles/.

Continue the spec (and, optionally, the design) for feature the user's request that followed this skill invocation (default: the current feature).

Context: read only that feature's spec.md (and its ui.md if continuing design) plus the structure of @.amby/templates/spec.md. This command extends an existing feature — it is not specify (which starts a new feature) nor clarify (which only resolves [NEEDS CLARIFICATION] markers).

  1. Resolve the feature dir specs/NNN-slug/. If it — or its spec.md — cannot be found, report a clear error and make no changes.
  2. Done-guard. If the spec.md frontmatter status: is done, make no edits: tell the author the feature is complete and to run /amby.specify for a new feature. Stop here.
  3. Otherwise continue in place (patch, never regenerate — Principle 3):
    • Add new user stories (US-#), requirements (FR-###), and success criteria (SC-###), each taking the next available number. Preserve every existing id and its text verbatim.
    • Refine existing items only where the author asked; keep their ids stable.
    • New requirements use EARS (SHALL / WHEN / WHILE / IF-THEN / WHERE); new acceptance criteria use Given/When/Then — consistent with specify.
    • Leave any story already marked status: done untouched; you may still add new stories.
  4. Set the spec.md frontmatter status: to in-progress.
  5. Design (optional). If the author is continuing the UI/design and ui.md exists, extend it in place, preserving existing sections. If ui.md does not exist, do not create it here — direct the author to run /amby.design.
  6. Keep edits minimal and token-frugal; cite the constitution by principle number where relevant.

Report what you added or changed, by id.