What problem does it solve?
It structures the authoring of issue-spec change artifacts so proposals, SPECs, QUESTIONs, designs, and TASKs follow a consistent typed-ID and phase workflow instead of ad-hoc issue text.
Core Features & Use Cases
- Typed Artifact Authoring: Creates proposal, Design, SPEC, QUESTION, and TASK artifacts with canonical ID rules like QUESTION-44001 scoped per issue.
- Blocking Question Tracking: Records every unresolved decision as a typed QUESTION with choice models rather than leaving open decisions in prose.
- Canonical Comment Generation: Generates SPEC comments with testable WHEN/THEN requirements and TASK comments covering execution planning and ownership.
- Use Case: When starting a new change in the higress repository, run the propose workflow to create the proposal issue, discover open questions, and produce SPEC and TASK comments ready for implementation planning.
Quick Start
Ask the assistant to run /issue-spec:propose to draft a proposal, SPEC, and TASK plan for your issue.