When should I update SPEC.md with a checked criterion?

Only after the criterion has been fully verified by tests, QA, or acceptance criteria.

Is it okay to update multiple criteria at once?

Yes, but ensure each item is genuinely verified before marking it complete.

How should verification be documented?

Include brief evidence or references to tests, QA results, or test logs alongside the update.

nancy-update-spec

Scanned

npx machina-cli add skill srobinson/helioy-plugins/nancy-update-spec --openclaw

Files (1)

SKILL.md

364 B

Update Spec

To mark a criterion complete, edit SPEC.md:

# Before
- [ ] All tests pass

# After
- [x] All tests pass

Only mark criteria when they are verified, not just implemented.

Source

git clone https://github.com/srobinson/helioy-plugins/blob/main/plugins/helioy-tools/skills/nancy-update-spec/SKILL.mdView on GitHub

Overview

This skill explains how to update SPEC.md by turning a checkbox from unchecked to checked once a criterion is fully verified. It ensures only truly verified success criteria are marked, avoiding premature or incorrect updates. Use it when a criterion has been confirmed and should be reflected in SPEC.md.

How This Skill Works

Locate the relevant criterion in SPEC.md, ensure it is fully verified, then replace the line "- [ ] <criterion>" with "- [x] <criterion>". Commit and document the verification to keep SPEC.md in sync with validated outcomes.

When to Use It

A criterion has been fully verified by tests or QA and should be marked complete
A new acceptance criterion has been validated and added to SPEC.md
Before releasing, you confirm that all verifiable criteria are checked off
During code or spec audits, you verify which items can be marked as complete
After a bug fix or feature implementation passes verification and live checks

Quick Start

Step 1: Identify the verified criterion in SPEC.md
Step 2: Confirm it is fully verified, not just implemented
Step 3: Change to "- [x]" and commit the update

Best Practices

Only mark criteria that are truly verified, not just implemented
Keep SPEC.md formatting consistent with the checklist style
Avoid bulk-checking; verify each item before updating
Document any verification steps or test evidence alongside the update
Review changes with peers to prevent incorrect completions

Example Use Cases

PR: All tests pass verified by CI; update SPEC.md to check the 'All tests pass' criterion
QA confirms feature behavior matches spec; mark corresponding line as checked
New acceptance test added and passes; update SPEC.md accordingly
Post-release audit shows performance target achieved; verify and check the item
Regression check passed after fix; update SPEC.md to reflect verification

Frequently Asked Questions

Add this skill to your agents