logvalet-spec-to-issues

To break a design specification into actionable backlog issues, you provide a spec file path or paste the spec text. The skill decomposes the document into structured tasks with clear titles, descriptions linked to spec sections, and dependency notes.

Yes, you can preview backlog tasks before creation from a requirements document using the dry-run preview feature. The skill generates an issue list for your review and requires user confirmation before bulk creating the tracked tasks.

Yes, spec-to-task decomposition supports optional epic and child relationships for complex specs. It structures properly scoped tasks based on sections and requirements, ensuring traceability back to the source specification.

The best way to convert a feature spec into structured project planning tasks is using a decomposition tool that parses multiple sections of a design walkthrough. It enables bulk creation of tracked tasks with dependency notes and scoping.

Yes, you can use this skill with a multi-section requirements document. It applies to feature specs, requirements documents, and design walkthroughs across multiple sections, breaking them down into structured backlog issues.

A limitation when decomposing a spec into backlog issues is the requirement for user confirmation before creation. Additionally, the parent and child epic relationships are optional, meaning complex task hierarchies require manual structuring during the review phase.