What problem does it solve? When a task folder is closed and sorted out, teams lose the reasoning behind past decisions unless it is captured in a consistent, findable archive record. This Skill defines exactly what goes into a record in docs/archive/, how it is named so it can be found without an index, and when it must be pruned. ## Core Features & Use Cases - File-name-as-index convention: Records are named RT-<task number>-<branch slug>.md (epics use a -line suffix), enabling lookup by subject, task number, or content via grep. - Content rules: Specifies what belongs in a record (the request grill in the owner's words, decisions with arguments, the price of the decision) and what does not (plans, progress logs, after-the-fact edits). - Lifecycle management: Records live one week, then are pruned with node tools/archive-prune.mjs (dry run by default, --apply to remove) and guarded by node tools/check-archive-age.mjs in the push gate. - Use Case: After merging a branch for task RT-1130, sort out the closed task folder, write the archive record with the owner's answers and key decisions, and verify no record has overstayed its week. ## Quick Start Ask the assistant to sort out the closed task folder and write its archive record into docs/archive following the naming and content rules.
