make-issue-spec

Create markdown issue specifications with acceptance criteria and implementation plans.

2.0k|126|Updated Jul 30, 2025
One-click install
npx skills add https://github.com/pchalasani/claude-code-tools --skill make-issue-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-issue-spec
Source: https://github.com/pchalasani/claude-code-tools/tree/main/plugins/workflow/skills/make-issue-spec
Command: npx skills add https://github.com/pchalasani/claude-code-tools --skill make-issue-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a markdown issue specification with a concise implementation plan, enabling teams to rapidly define tasks with clear scope, acceptance criteria, and a path to execution.

Core Features & Use Cases

  • Structured Issue Specs: Generate a markdown file at issues/YYYYMMDD-blah-blah.md containing a problem statement, goals, acceptance criteria, and a short implementation plan.
  • Ambiguity Clarification: Prompts the user to answer questions for parts that are unclear or under-specified before finalizing the spec.
  • Git-ready Outputs: Provides a filename and content suitable for staging in a Git workflow.

Quick Start

Use the make-issue-spec skill to draft an issue specification for a new feature, saving it to issues/YYYYMMDD-name.md with a clear problem statement and concise implementation plan.

Frequently Asked Questions about make-issue-spec

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

FAQPage Schema
How do I generate a markdown issue specification for project management tasks?

An issue specification in markdown provides a structured problem statement, goals, acceptance criteria, and a short implementation plan. It is needed to define task scope and execution paths for project management workflows.

How do I clarify ambiguities before finalizing an issue spec?

To create an issue spec, provide a brief description of the feature or ticket. The skill generates a date-stamped markdown file with a problem statement, acceptance criteria, and an implementation plan, then prompts you to resolve any ambiguities.

Does the generated issue spec work with Git workflows?

Yes, the generated issue spec is Git-ready. It produces a markdown file with a standardized filename and content structure suitable for staging directly within a Git workflow repository.

What is the naming convention for the generated issue specification files?

Before using this skill, gather project requirements and feature details to input. This provides the context needed to generate a markdown issue spec with accurate problem statements and implementation plans.

What should I do if my issue spec has unclear or under-specified requirements?

After generating the issue spec markdown file, stage and commit it to your Git repository. This integrates the structured problem statement and implementation plan into your project management workflow for team tracking.