dev-issues

To convert unstructured brain-dumps into actionable development issues, this skill decomposes long-form text streams into discrete issue files. It applies strict collision-checking against existing notes and enforces concrete scope and acceptance criteria to enable downstream execution.

Tracking feature ideas and refactor notes without duplicates requires collision-checking against an existing notes inbox. This process updates overlapping items rather than duplicating them, ensuring a clean, ordered set of individually-actionable issue files.

Issue decomposition handles half-formed ideas by breaking down long-form brainstorms into discrete, well-shaped work items. It asks clarifying questions only where a genuine decision is required, capturing every thought as an issue a downstream agent can execute.

You can use these generated issues directly with your development loop. Each issue file enforces monotonic numbering and concrete acceptance criteria, producing notes specifically designed for a downstream agent or dev-loop to pick up and execute.

Converting a brain-dump into tracked issues does not require manual batch formatting. You simply tag an unstructured stream of features, bugs, and ideas, and the system automatically structures, collision-checks, and commits the batch of notes.

A limitation when decomposing long-form text into issue files is that the process enforces strict collision-checking and monotonic numbering at a flat top level. It will pause to ask clarifying questions only where a decision is genuinely yours to make.