revision

Audits project folders by categorizing topics, updating missions, and archiving completed work.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/alatyshau/duet --skill revision-alatyshau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revision
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/modes/revision
Command: npx skills add https://github.com/alatyshau/duet --skill revision-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project folders accumulate topics over time, causing missions to drift out of date and completed work to clutter active files. This Skill performs a structured audit of an entire project folder so the index, mission, and roadmap stay aligned with reality. ## Core Features & Use Cases - Topic Audit: Evaluates every topic file against the project mission and categorizes each as ЯДРО (core), ОРБИТА (orbit), or АРХИВ (archive). - Mission Evolution: Checks whether the current mission formulation still covers all core topics and proposes updates when it does not. - Controlled Archiving: Renames completed topic files with a YYMMDD_ date prefix and moves them to the archive section of index.md, but only after explicit user approval. - Use Case: After finishing a major milestone with 15 accumulated topic files, run a revision to archive 5 completed topics, move 2 off-mission topics to orbit, and refresh the roadmap in index.md. ## Quick Start Enter REVISION mode and audit this project folder, categorizing all topics and proposing mission and roadmap updates for my approval.

Frequently Asked Questions about revision

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

FAQPage Schema
How do I audit a project folder with many accumulated topics?

Enter REVISION mode, which reads index.md for the mission and roadmap, then evaluates each topic file for mission fit. It produces a summary report categorizing topics as ЯДРО, ОРБИТА, or АРХИВ before making any changes.

When should I run a project revision instead of a topic review?

Run a revision when 10 or more topics have accumulated, the mission seems outdated, a major milestone completed, or a new phase is starting. REVIEW covers a single topic and its artifacts, while REVISION audits the entire project folder.

Does the revision process modify files automatically?

No. The revision first generates a report in chat with categorization, mission proposals, and archiving suggestions. Changes to index.md and file renames are applied only after explicit user approval.

How are completed topics archived in the project folder?

Completed topic files are renamed with a YYMMDD_ date prefix, moved to the АРХИВ section of index.md, and given a brief outcome summary. Links in other files referencing the topic are updated as needed.

What happens to topics that do not fit the project mission?

Off-mission topics are categorized as ОРБИТА, meaning they remain legitimate but wait for their own project folder. The revision records the reason and proposed fate for each orbit topic rather than deleting them.