Documentation
README
Create Issue
Issues in this repo come in different shapes because the work does: a plan task carries acceptance criteria written months in advance; a bug carries a repro; a spike carries a question and a timebox. One rigid template can't serve all of these, so this skill generates the right body per type and files it with gh issue create.
The specs are the source of truth. Never invent scope or acceptance criteria β pull them from the docs, and if a plan task is missing something, flag the gap to the user instead of papering over it.
Step 1 β Classify the request
This is the opening of the README. Read the full README on GitHub.