update-spec

Automate specification document review and revision planning.

5|1|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ncukondo/reference-manager --skill update-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-spec
Source: https://github.com/ncukondo/reference-manager/tree/main/.claude/skills/update-spec
Command: npx skills add https://github.com/ncukondo/reference-manager --skill update-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically review and revise project specifications to keep documentation accurate, consistent, and actionable.

Core Features & Use Cases

  • Automates spec review and revision planning for spec/_index.md and related documents.
  • Records architectural decisions with ADRs to ensure traceability and accountability.
  • Enables roadmap-aligned task planning and documentation updates with minimal coupling to code.

Quick Start

Ask this skill to review spec/_index.md and propose an updated specification plan.

Frequently Asked Questions about update-spec

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

FAQPage Schema
How do I automate spec review and keep project documentation current?

Automating spec review evaluates specification documents like spec/_index.md to keep documentation accurate and actionable. This process systematically revises project specifications, maintaining alignment with development workflows through minimal code coupling.

What is the best way to record architectural decisions for spec traceability?

Recording architectural decisions uses ADRs to ensure traceability and accountability. ADRs capture decision rationale within specification documents, providing clear historical context for development teams during spec revision.

How do I update a roadmap and plan tasks aligned with revised specifications?

Updating a roadmap aligned with revised specifications requires evaluating the updated spec plan to derive actionable tasks. This ensures task planning remains coupled to documentation rather than directly to source code.

Does spec revision work without tightly coupling to my codebase?

Spec revision works with minimal coupling to code, focusing on documentation accuracy. It enforces modular file organization and frontmatter-driven discovery, ensuring specifications remain independent referenceable assets.

When do I need to revise specification documents in a TDD workflow?

Revising specification documents in a TDD workflow is needed when project specs drift from implementation. It enforces English prose and modular organization to keep specs actionable for automated test generation.