update-spec

Mark verified acceptance criteria as complete in SPEC.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of recording and validating completion of acceptance criteria by updating SPEC.md only for criteria that have been verified.

Core Features & Use Cases

  • Selective completion: marks only verified criteria as complete in SPEC.md.
  • Auditable change tracking: leaves a clear record of what was verified.
  • Use Case: In a sprint, QA verifies a feature and updates SPEC.md to reflect completion status.

Quick Start

Open SPEC.md, locate a verified criterion, and mark its checkbox as complete by replacing [ ] with [x].

Frequently Asked Questions about update-spec

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

FAQPage Schema
How do I mark verified acceptance criteria as complete in SPEC.md?

To mark verified acceptance criteria as complete in SPEC.md, locate the verified criterion and replace the checkbox syntax [ ] with [x] to document completion status and maintain an auditable change log.

What is the best way to track verification progress for project acceptance criteria?

Tracking verification progress for acceptance criteria involves updating a SPEC.md file to selectively mark only verified requirements as complete, ensuring completed features are documented and auditable across the project lifecycle.

Can I update SPEC.md to reflect completion status after QA verifies a feature?

Yes, you can update SPEC.md to reflect completion status after QA verifies a feature by marking the checkbox of the specific verified criterion as complete, which leaves a clear record of what was tested.

How does selective completion work when updating project specifications?

Selective completion works by enforcing that only verified criteria in the SPEC.md file are marked complete, preventing unverified requirements from being checked off and maintaining an auditable record of project progress.

Does this SPEC.md update approach work for any project management workflow?

Yes, this SPEC.md update approach works for any project management workflow where SPEC.md tracks acceptance criteria, verifications, and progress across features, requiring no specific dependencies to function.

Why should I only mark verified success criteria as complete in project documentation?

You should only mark verified success criteria as complete in project documentation to ensure an accurate representation of project progress and to maintain a reliable, auditable change log for stakeholder review.