Loading...
Loading...
Found 4 Skills
Comprehensive documentation audit and generation. Launches parallel agents for high-level docs, module-level docs, decision records, and state diagrams. Use when: documentation gaps, post-implementation docs, README updates, architecture docs.
Post-implementation reality check. Run after tests pass, before declaring done. Use when completing a feature, bug fix, refactor, or integration — or when asked to verify, sanity check, or confirm something actually works.
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
Review code after implementation work to identify design flaws, abstraction issues, or maintenance risks that only became clear once real code was written. Use whenever the user asks whether a recent change exposed architectural problems, whether an abstraction is fighting the implementation, or whether a refactor is justified. Be conservative and avoid suggesting refactors without concrete evidence of recurring cost or complexity.