spec-improve

Audit and rewrite technical specifications for clarity and testability.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/codacy/codacy-specs --skill spec-improve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-improve
Source: https://github.com/codacy/codacy-specs/tree/main/skills/spec-improve
Command: npx skills add https://github.com/codacy/codacy-specs --skill spec-improve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of vague, ambiguous, or incomplete specifications that cause AI agents to make incorrect assumptions, fail to implement requirements, or produce unverifiable code.

Core Features & Use Cases

  • Spec Audit: Scores specifications on a 0–100 rubric across critical dimensions like acceptance criteria, error handling, and testability.
  • Guided Clarification: Asks focused, one-at-a-time questions to fill critical gaps in requirements.
  • Spec Rewrite: Produces a fully structured, AI-agent-ready specification using proven templates.
  • Use Case: Before starting work on a Jira ticket or a local spec file, use this skill to ensure the requirements are clear, testable, and unambiguous for an AI agent.

Quick Start

Use the spec-improve skill to audit the specification in the current file and rewrite it to be ready for implementation.

Frequently Asked Questions about spec-improve

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

FAQPage Schema
How do I audit Jira or Linear tickets for AI-agent readiness?

To audit Jira or Linear tickets for AI-agent readiness, this skill detects spec types and scores them on a 0–100 rubric across critical dimensions like acceptance criteria, error handling, and testability. It requires integration with issue tracking MCP servers to perform full audits.

What is the best way to rewrite vague technical specifications for AI implementation?

The best way to rewrite vague technical specifications is to use a guided clarification process that asks focused questions to fill gaps, then produces a fully structured, AI-agent-ready specification using proven templates.

Does spec-improve work with local file sources and GitHub?

Yes, spec-improve works with local file sources and GitHub. It audits and rewrites technical specifications across Jira, Linear, GitHub, and local files by applying quality rubrics to ensure requirements are clear and unambiguous.

How are specification gaps identified and clarified?

Specification gaps are identified through a scoring rubric, then clarified via guided questions asked one at a time. This focused clarification loop fills critical gaps in requirements before rewriting the spec.

Do I need MCP servers to audit specifications?

Yes, you need issue tracking MCP servers and local file access to perform full audits, clarification loops, and write-back updates across platforms like Jira and Linear.

When should I audit specs before AI implementation?

You should audit specs before starting work on a Jira ticket or local spec file to ensure the requirements are clear, testable, and unambiguous, preventing AI agents from making incorrect assumptions or failing to implement requirements.