doc-tasks-fixer_skill

This skill automatically applies fixes to TASKS documents from review reports, ensuring structure, links, and IDs are corrected for iterative quality

Python

9

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vladm3105/aidoc-flow-framework --skill doc-tasks-fixer

SKILL.md41.6 KB

Overview

This skill automates fixes to TASKS (Implementation Tasks) documents by reading the latest review report and applying corrective changes. It closes the loop between issue discovery and document correction so TASKS can iterate toward compliance and implementation readiness. The skill produces a fixed TASKS file and a fix report capturing all applied changes.

How this skill works

The skill locates the latest review report for a given TASKS file, parses and categorizes reported issues, and executes a staged fix pipeline. Phases run in order: structural fixes, creating missing files, repairing broken links, normalizing element IDs, resolving content gaps, and updating traceability references. It can auto-generate stubs (contracts, dependencies, iplans), adjust relative paths after moves, and produce a follow-up fix report; optional re-run of the reviewer supports iterative cycles.

When to use it

After running a review that produced a TASKS review report
As part of an iterative Review -> Fix -> Review quality loop
In CI/CD pipelines to enforce documentation quality gates
When multiple TASKS need batch corrections based on a report
To repair malformed or incomplete implementation contract structures

Best practices

Run doc-tasks-reviewer first so this skill has actionable issues to fix
Keep a commit or backup before automated moves or large structural changes
Treat generated stubs as drafts that require human completion and validation
Tune iterative thresholds: re-run reviewer until score meets acceptance or iterations hit a limit
Prefer relative paths in TASKS to reduce link breakage after moves

Example use cases

Move a TASKS file into the required nested folder and update all relative links automatically
Create a missing contracts.py stub and dependencies.yaml when referenced but absent
Convert legacy or invalid element IDs to valid TASKS type codes across the document
Fix broken SPEC/TSPEC links and update absolute paths to correct relative paths
Replace template dates with current dates and flag TODO/TBD placeholders for manual completion

FAQ

No. The skill flags TODO/TBD placeholders and fills only trivial templates (dates, author metadata). Human review is required for substantive content.

Will automated moves break other documents that link to the TASKS file?

The skill updates relative links inside the moved TASKS file and attempts to update known upstream references, but you should review and run the reviewer across related docs to catch external link updates.