spec-writing

Plan and write specification document changes with a SPECFILES.md manifest.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/jtlapp/agent-plugins --skill spec-writing-jtlapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-writing
Source: https://github.com/jtlapp/agent-plugins/tree/main/plugins/spec-writing/skills
Command: npx skills add https://github.com/jtlapp/agent-plugins --skill spec-writing-jtlapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures software specifications are precise, consistent across documents, and robust by guiding users through planning and writing changes.

Core Features & Use Cases

  • Manifest-Driven Specification: Manages a set of specification documents via a SPECFILES.md manifest.
  • Terminology & Concept Management: Enforces clear definitions and progressive explanation of terms and concepts.
  • Requirements Compliance: Verifies changes against project requirements and constraints.
  • Robustness & Scenario Tracking: Prompts consideration of edge cases and tracks scenarios.
  • Use Case: When planning a new feature, use this skill to ensure all related specification documents (requirements, model, behavior, glossary) are updated consistently, new terms are defined, and potential issues are identified before implementation.

Quick Start

Use the spec-writing skill to initialize a new specification manifest and starter files.

Frequently Asked Questions about spec-writing

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

FAQPage Schema
How do I keep software specification documents consistent across multiple files?

To keep software specification documents consistent, use a manifest-driven approach that tracks all files via a SPECFILES.md manifest, enforcing terminology discipline and requirements compliance across the entire document set.

What is the best way to define and manage terminology in technical requirements documents?

The best way to manage terminology in technical requirements documents is to enforce clear definitions and progressive explanation of terms. This ensures that concepts are defined consistently and tracked across all related project specifications.

How do I plan changes to a software design document while checking for edge cases?

To plan changes to a software design document and check for edge cases, you need a process that prompts scenario tracking. This approach verifies modifications against project requirements and constraints while identifying potential robustness issues before implementation.

Can I use a manifest to maintain requirements compliance across a set of project specifications?

Yes, you can use a SPECFILES.md manifest to maintain requirements compliance across project specifications. The manifest acts as a central registry, allowing you to verify that document changes align with defined project requirements and constraints.

When do I need a dedicated tool for writing precise software specifications?

You need a dedicated tool for writing precise software specifications when planning a new feature that requires updating multiple related documents. It ensures requirements, models, behaviors, and glossaries remain aligned and robust before implementation begins.