issue-writer

To write clear GitHub issues focused on requirements, use a structured template that separates the problem, expected outcomes, acceptance criteria, and constraints. This ensures issues describe what needs to be done without specifying how to implement it.

The best way to write acceptance criteria for agile tracking is using a tracker-agnostic format. State behavior-focused outcomes and constraints clearly so issues remain usable across Jira, GitHub, Linear, and Asana for cross-functional teams.

Yes, you can use the same issue writing format for Jira and GitHub trackers. The generated issues are tracker-agnostic and behavior-focused, ensuring they remain usable across languages, tech stacks, and different tracking platforms.

Structure a requirements-first issue by drafting a template that captures the problem, expected outcomes, and constraints. This reduces ambiguity and misalignment by keeping the issue behavior-focused and free of implementation specifics.

Teams misalign on vague issue requests because they lack structured acceptance criteria and clear constraints. Separating the problem statement from requirements ensures issues are actionable and describe expected behavior rather than implementation.

You should avoid including technical implementation specifics in issue tracking when planning new features or requirement updates. Issues should remain behavior-focused and tracker-agnostic to prevent misalignment across cross-functional teams and tech stacks.