Track issues with the issy CLI

Authoring Issues

Issues describe what needs to be done and why. Keep them high-level unless the user provides specific details.

What to Include

• Problem/Overview: What's wrong or what's needed (1-2 paragraphs)
• Proposed Solution: High-level approach
• Acceptance Criteria: Optional - what "done" looks like from user perspective
• Verification: Optional but encouraged - how to prove the issue is resolved (see below)
• Future Considerations: Optional - related ideas for later
• References: Optional - links to related docs, issues, or resources

Verification Guidance

When possible, include verification steps or hints that tell the implementing agent how to prove the issue is resolved. This helps ensure work is actually verified before being marked complete.