Proposal Status — Lifecycle Transitions

Transition a proposal through its lifecycle states with validation and side-effects.

Command

/proposal-status <number-or-path> <new-status> [--module <path>] [--root]

Arguments

Workflow

1. •

   Parse arguments. Extract the proposal identifier and target status from $ARGUMENTS.

2. •

   Locate the proposal. If a number is given, search for NNN-*.md in the appropriate docs/proposals/ directory. If a path is given, use it directly.

3. •

   Read current status. Parse the proposal's frontmatter to get the current status field.

4. •

   Validate the transition. Check against the state machine defined in reference/valid-transitions.md:

   code

   draft ──→ in-review ──→ accepted
                       ──→ rejected
                       ──→ superseded
   

   • •If the transition is invalid, report an error with the legal transitions from the current state. Example: "Cannot transition proposal 001 from 'draft' to 'accepted'. Valid transitions from 'draft': in-review."
   • •If the current status is terminal (accepted, rejected, superseded), report: "Proposal 001 has reached terminal status '<status>' and cannot be transitioned."
5. •

   Update the proposal. If valid:

   • •Update the status field in frontmatter
   • •Update the updated field to today's date
6. •

   Handle side-effects:

   On accepted:

   • •Prompt the user: "Proposal NNN has been accepted. Create an implementation plan? Use /new-plan <title> --from-proposal NNN."

   On superseded:

   • •Prompt for the superseding proposal number
   • •Update the superseded_by field in frontmatter with the superseding proposal's number
7. •

   Confirm the transition. Report the updated status and any next steps.

State Machine

Read reference/valid-transitions.md for the complete state machine definition, including conditions and side-effects for each transition.

Reference

• •reference/valid-transitions.md — State machine definition with legal transitions, conditions, and side-effects