issue-workflow

Decomposing specifications into GitHub issues involves splitting work into independent, testable units using standardized templates for issue bodies and detailed `.issue/spec.md` files to capture all necessary documentation.

Organizing project management documentation is best handled by establishing a consistent `.issue/` directory structure convention, storing detailed issue-specific documentation alongside standardized GitHub issue bodies.

Managing issue dependencies and granularity requires a methodology that splits specifications into manageable units and enforces quality through mandatory checklist items for issue decomposition and documentation.

Yes, you can use standardized templates for GitHub issue bodies and `.issue/` directory files to systematically capture component details, ensuring necessary documentation is consistently organized for development.

You need a structured workflow for breaking down complex specifications when a new feature is defined in a PRD and an AI agent must systematically create individual GitHub issues for each component while ensuring quality through mandatory checklists.

No, issue-workflow has no external dependencies; it provides a standalone methodology and standardized formats for decomposing specifications into GitHub issues and organizing `.issue/` documentation without requiring additional tools.