issue-spec

To draft precise issue specifications, use a standardized template covering the problem, approach, files to modify, acceptance criteria, out of scope, and test plan. This backend-agnostic approach reduces ambiguity and rework across trackers like Beads, Linear, GitHub Issues, and Jira.

An effective issue specification template includes Problem, Approach, Files to Create/Modify, Content Source, Acceptance Criteria, Out of Scope, and Test Plan sections. It requires minimal frontmatter with a name and description to support drafting and auditing issues across platforms.

Yes, this issue specification format works with Linear and Beads. It provides backend-agnostic guidance with sections to reference related documentation and storage backends specifically for Beads and Linear, ensuring consistent issue drafting across platforms.

To manage parent-child task specifications in a convoy workflow, use the convoy-spec support. This allows you to draft per-item work item specs while maintaining hierarchical relationships, ensuring all child tasks align with the parent issue's approach and acceptance criteria.

Acceptance criteria and a test plan are needed in issue specs to reduce ambiguity and prevent rework. They define clear completion standards and verification steps, ensuring the implemented approach solves the stated problem and meets quality expectations before closing the issue.

No, this issue specification template is backend-agnostic and has zero dependencies. It prescribes a minimal frontmatter requirement of just a name and description, allowing you to draft and audit issues across any tracker without installing specific platform integrations.