skills.rest
real-case
real-caseCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

task-audit

Lints the task spec corpus for duplicate numbers, slug collisions, and dangling dependencies.

Updated Apr 16, 2026
Search Tags:#task management#consistency check#lint#read-only#mcp tool#spec audit#markdown specs
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill task-audit-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-audit
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/task-audit
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill task-audit-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Task spec directories accumulate inconsistencies over time: duplicate numbering, colliding slugs, broken dependency references, and missing seals. This Skill audits the entire spec corpus under .marvin/task in one read-only pass and reports every finding with remediation guidance. ## Core Features & Use Cases - Corpus-wide consistency checks: Detects malformed specs, invalid statuses, duplicate numbers, slug collisions, dangling depends_on references, missing seals, and numbering holes via the spec MCP tool. - Severity-ranked findings with remediation: Errors and warnings are grouped by class, each paired with a concrete fix and a recommended fix order. - Read-only guarantee: The audit changes nothing; every fix remains the user's decision. - Use Case: Before starting the next task, ask for a spec audit to confirm no two specs share a number and no depends_on row points at a spec that does not exist. ## Quick Start Ask the assistant to audit the specs and check .marvin/task for duplicate numbers or dangling dependencies.

Frequently Asked Questions about task-audit

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

FAQPage Schema
How do I check my task specs for duplicate numbers or broken references?▼

Run the spec audit, which calls the spec MCP tool's audit action over the whole .marvin/task directory. It reports duplicate numbers, slug collisions, and dangling depends_on references as errors with the affected files named.

What does the spec corpus audit actually check?▼

It checks seven finding classes: malformed files, invalid statuses, duplicate numbers, slug collisions, dangling depends_on references, missing contract seals, and numbering holes. The first five are errors; missing seals and holes are warnings.

Does the spec audit modify or fix my spec files?▼

No, the audit is strictly read-only. It renders findings with remediation guidance and a recommended fix order, but every renumber, rename, or re-seal is left to the user through commands like /marvin:task-start.

Should I renumber specs to close numbering holes found by the audit?▼

No. Numbering holes are warnings that usually represent withdrawn history. Renumbering rewrites filenames that depends_on rows, PR bodies, and handoff documents already reference, turning one warning into several errors.

When should I use task-audit instead of task-start or sec-scan?▼

Use task-audit for corpus-level consistency of the spec directory. Single-spec contract validity is the Definition-of-Ready gate handled by /marvin:task-start, and vulnerability checks belong to /marvin:sec-scan.

Related Skills

Explore More Software Engineering Skills→
deandumdeandum
3

spec-generation

Create and validate docs/specs/<slug>/ directories with standard spec.md frontmatter.

Community
Advanced
CityBear3CityBear3

agent-teams-driven-development

Coordinate implementer and reviewers to execute plan tasks with iterative fix loops.

Community
Advanced
happysasha18happysasha18
1

text-audit-pack

Binds the external text-audit skill to live-spec pack lints, paths, and reader rules.

Community
Intermediate
wuji-technologywuji-technology

design-handoff

Extract design tokens, component specs, and interaction annotations from Figma prototypes.

Official
Advanced