What problem does it solve? Converting a long design conversation into a durable, structured specification is tedious and error-prone; decisions made by the human get lost or confused with agent inference. This Skill turns the current conversation context into a complete Spec and publishes it to the project issue tracker without re-interviewing the user. ## Core Features & Use Cases - Spec Synthesis: Generates a full Spec from existing conversation context, including problem statement, user stories, implementation decisions, testing decisions, and acceptance criteria. - Human Decision Capture: Records every HITL call (testing seams, trade-offs, rejected alternatives) in a dedicated Human Decisions section so downstream slicing and autonomous execution preserve human judgement. - Tracker Publishing with Labels: Publishes the Spec with type:spec and needs-slicing labels, creates territory tag:<value> labels on demand, and enforces a cascade gate that blocks publishing while .red/ docs are unlanded. - Use Case: After a design discussion about a new feature, run the Skill to produce a tracker-ready Spec that /to-tickets can later slice into implementable child issues for /afk workers. ## Quick Start Ask the agent to turn the current conversation into a Spec and publish it to the issue tracker, optionally passing territory tags with --tags a,b.
