agentsclimarketplace

Validate specs workflow

Skill itsjavi/skills/skills/validate-specs-workflow

Coding agent skills to help projects adopt spec-driven development with durable product memory documents

Install
npx -y skills add itsjavi/skills --skill validate-specs-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Specs Workflow Validator

Validate a project planning workflow without judging product strategy or implementation quality.

Workflow

  1. Preserve git index state. Do not stage, unstage, commit, amend, reset, or discard files unless explicitly asked.

  2. Resolve the planning root:

    • Use the path named by the user when provided.
    • Otherwise prefer a directory with GUIDE.md and MILESTONES.md.
    • Check common roots in this order: .specs/, docs/, project-specs/, .agents/specs/, ai/.
    • If no planning root exists, report that setup is missing and recommend setup-specs-workflow.

  3. Run the bundled validator script from this skill folder:

    node skills/validate-specs-workflow/scripts/validate-specs-workflow.mjs <planning-root>

    If running from outside this skills repository, use the absolute path to the script.

  4. Read only files named in validator findings when extra explanation is needed.

  5. Report findings grouped by severity:

    • FAIL: broken contract that should be fixed before relying on the workflow
    • WARN: incomplete or likely-stale workflow content
    • INFO: useful follow-up or optional improvement

What The Script Checks

  • Required files and directories exist.
  • Core templates exist.
  • Plan filenames use MMM-PPP-slug.md.
  • Checkpoint filenames use MMM-PPP-slug-LETTER.md and link to an existing plan.
  • Plan files include required sections, including Changelog Impact.
  • Bug-fix and checkpoint templates/records include Changelog Impact.
  • Changelog Impact values use allowed categories.
  • MILESTONES.md and BUG_FIXES.md links point to existing local files when they target workflow records.
  • CHECKS.md has at least one concrete command.
  • MANUAL_QA.md has at least one non-placeholder workflow row or workflow detail.
  • Required docs are not mostly empty blueprint placeholders.
  • Generated workflow docs do not reintroduce plan-coord recommendations.

Limits

The validator is intentionally lightweight. It does not decide whether a milestone is wise, a plan is complete enough for the business, or a manual QA flow is semantically correct. It checks structure, obvious omissions, and workflow hygiene.

Final Response

Report:

  • planning root checked
  • command run
  • count of fails, warnings, and info findings
  • highest-priority fixes with file paths

Keep the response concise. Do not paste the full script output if it is long; summarize and include the command so the user can rerun it.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.