trevoke/recs-files
Skills for working on a project whose records are the source of truth.
Use when asked to build, add, change or fix what a system does - a feature, a component, a behaviour - before any record, plan or implementation for it — for projects that keep records as their source of truth.
Use when you have a written implementation plan to execute in a separate session with review checkpoints — for projects that keep records as their source of truth.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup — for projects that keep records as their source of truth.
Use when an existing project is adopting records as its source of truth and has no records yet, or only scattered docs — before any other recs-* skill can be used there.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation — for projects that keep records as their source of truth.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — for projects that keep records as their source of truth.
Use when executing implementation plans with independent tasks in the current session — for projects that keep records as their source of truth.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes — for projects that keep records as their source of truth.
Use when implementing any feature or bugfix, before writing implementation code — for projects that keep records as their source of truth.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification — for projects that keep records as their source of truth.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always — for projects that keep records as their source of truth.
Use when you have a spec or requirements for a multi-step task, before touching code — for projects that keep records as their source of truth.
Use when a decision, definition, workflow, feature, or exact failure text needs to enter a project's records, when a record needs superseding, merging, splitting, retiring or clarifying, or when an agreed term must be swept across the codebase — for projects that keep records as their source of truth.