Organize and clean up specification documents after implementation completion. Removes implementation details while preserving essential context for future refactoring.
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
ESM-ify source files that arrive from a pre-ESM branch when merging into apps/app. Use after merging any branch that predates the v8 ESM migration (long-lived feature branches cut from v7-era master, v7.5 maintenance work) into master or a v8 branch — a git…
GROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.
Write tests that verify observable behavior (contract), not implementation details. Auto-invoked when writing or reviewing tests.
Evaluate the quality of GROWI's suggest-path output by judging each proposed save-path as o (usable) / △ (usable but improvable) / x (not usable) for a document, with a wiki-agnostic plausibility rubric — NOT by matching one "correct" path. For each document…
Fix broken symlinks in .next/node_modules/ — diagnose, decide allowlist vs dependencies, and verify