issue-tracking

Manage project issues as version-controlled markdown files via the issy CLI.

4|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/miketromba/issy --skill issue-tracking-miketromba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-tracking
Source: https://github.com/miketromba/issy/tree/main/skills/issue-tracking
Command: npx skills add https://github.com/miketromba/issy --skill issue-tracking-miketromba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and persist project issues without relying on external trackers by storing issues as human-readable, version-controlled markdown files that travel with your code and are discoverable by AI assistants.

Core Features & Use Cases

  • Natural language issue management: Create, read, update, list, and close issues using plain language via the issy CLI or an AI assistant.
  • Roadmap ordering & prioritization: Maintain a strict roadmap order with positional flags (--first, --last, --before, --after) and required priority and type metadata.
  • Verification and hooks: Encourage verification steps in issue bodies and support optional on_create/on_update/on_close hook files to surface context to agents.
  • Use Case: Ask your assistant to create a high-priority bug with verification steps and the skill will add a YAML-frontmatter issue file under .issy/issues and position it correctly in the roadmap.

Quick Start

Create a bug for the login redirect issue with high priority, include verification steps, and place it after issue 0002.

Frequently Asked Questions about issue-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage project issues as version-controlled markdown files in git?

Manage project issues as version-controlled markdown files by storing YAML frontmatter records under .issy/issues. This allows issues to travel with your code and remain diffable, providing traceable records without external trackers.

Can I create and prioritize issues using natural language in an AI-assisted workflow?

Create and prioritize issues using natural language via the issy CLI or an AI assistant. The system parses plain language to generate issue files, maintain strict roadmap ordering, and apply required priority and type metadata.

What is the best way to maintain roadmap ordering for issues in a git repository?

Maintain roadmap ordering for issues using positional flags like --first, --last, --before, and --after. This ensures strict positional tracking within your version-controlled markdown files.

Does issue tracking with markdown files support verification steps and post-action hooks?

Issue tracking with markdown files supports verification steps in issue bodies and optional on_create, on_update, and on_close hook files. These hooks surface context to AI agents during updates.

Can I use natural language issue management without external issue trackers?

Natural language issue management works without external trackers by storing human-readable markdown files directly in your git repository. This allows AI assistants to discover and update issues locally.

What are the limitations of managing issues as version-controlled markdown files?

Limitations of managing issues as markdown files include dependency on git repositories and local file storage under .issy/issues. It lacks real-time collaboration features found in external trackers but provides diffable traceability.