Run any Skill in Manus with one click

validate-specs-workflow

Stars1

Forks0

UpdatedMay 18, 2026 at 13:50

Use when the user asks to validate, audit, check, lint, or inspect a .specs planning workflow for structural consistency, missing required files, broken links, stale placeholders, invalid statuses, malformed plan/checkpoint names, missing changelog impact fields, or incomplete CHECKS.md and MANUAL_QA.md setup. Includes a bundled deterministic validator script.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

itsjavi

itsjavi/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	validate-specs-workflow
description	Use when the user asks to validate, audit, check, lint, or inspect a .specs planning workflow for structural consistency, missing required files, broken links, stale placeholders, invalid statuses, malformed plan/checkpoint names, missing changelog impact fields, or incomplete CHECKS.md and MANUAL_QA.md setup. Includes a bundled deterministic validator script.

Specs Workflow Validator

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

Workflow

Preserve git index state. Do not stage, unstage, commit, amend, reset, or discard files unless explicitly asked.
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.
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.
Read only files named in validator findings when extra explanation is needed.
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.

More from this repository

same repository

setup-specs-workflow

itsjavi/skills

Use when the user wants to bootstrap a docs-driven AI+human development workflow in a new project, including PRODUCT.md, MILESTONES.md, milestone records, BUG_FIXES.md, bug-fix records, BUSINESS_RULES.md, business-rule records, COORDINATION.md, decision records, plans, checkpoints, research notes, setup docs, CHECKS, MANUAL_QA, ENV_VARS, SECURITY, changelog impact fields, templates, and coding-agent instructions for following the workflow; also use when upgrading an older existing planning workflow to the current conventions.

2026-05-181

create-milestone

itsjavi/skills

Use when the user asks to create, draft, add, or update a milestone in an existing project planning workflow, including finding the planning root, reading GUIDE.md, choosing the next three-digit milestone number, creating or updating milestones/NNN-slug.md, and updating MILESTONES.md without duplicating milestone detail into the index.

2026-05-181

create-plan

itsjavi/skills

Use when the user asks to create, draft, add, or plan a new implementation plan in an established planning workflow, including finding the planning root, reading GUIDE.md, choosing the next milestone-scoped plan number, updating the target milestone record, creating a phase/checkpoint-ready plan file, and asking whether implementation should start afterward.

2026-05-181

document-decision

itsjavi/skills

Use when the user asks to document, capture, record, create, or supersede an architecture/product/security/operational decision in an existing project planning workflow, including ADR-style decision records for major durable choices. If called with no explicit decision text, infer the latest major durable decision from the current chat; if there are multiple plausible decisions or the decision is unclear, ask a concise clarifying question before editing.

2026-05-181

create-design-guidelines

itsjavi/skills

Create a design guide / design system spec document (typically DESIGN.md) for a web or mobile UI project. Trigger whenever the user asks to "create a design guide", "write a design system doc", "create DESIGN.md", "write design guidelines", "draft a style guide", or wants any general visual / UX style document an LLM or developer can use as a reference when building components, pages, or screens. Also trigger for design specs for a webapp, SPA, mobile app, dashboard, or component library — even when they don't say "design guide" verbatim. Accepts optional context like framework (React, Vue), styling (Tailwind, CSS), UI library (shadcn/ui, Base UI, Radix, MUI), brand color, theme name, and product name. With no arguments, inspects the current project to infer them; missing fields are left open rather than guessed.

2026-05-181

create-implementation-prompt

itsjavi/skills

Use when the user asks for a prompt to start a fresh chat/agent for implementing an existing project plan, e.g. "write a prompt for Plan 003-001", "create the next plan implementation prompt", or "handoff prompt for .specs/plans/MMM-PPP-*.md". Also useful to continue a plan implementation that was stopped and is still in progress. After generating the prompt, ask whether implementation should start now.

2026-05-181

name	validate-specs-workflow
description	Use when the user asks to validate, audit, check, lint, or inspect a .specs planning workflow for structural consistency, missing required files, broken links, stale placeholders, invalid statuses, malformed plan/checkpoint names, missing changelog impact fields, or incomplete CHECKS.md and MANUAL_QA.md setup. Includes a bundled deterministic validator script.

Specs Workflow Validator

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

Workflow

Preserve git index state. Do not stage, unstage, commit, amend, reset, or discard files unless explicitly asked.
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.
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.
Read only files named in validator findings when extra explanation is needed.
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

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.