Enforce .human file boundaries when editing code. Checks file protection levels (free, confirm, readonly) before modifying any file. Use when the workspace contains .human files or when about to edit, create, or delete files in a project that uses .human for ownership boundaries.
Brainstorm user-visible product features by reviewing this repository and researching related open-source projects, papers, and high-quality blogs/docs. Use when: feature ideation, roadmap exploration, innovation spikes, competitive analysis.
Consolidate completed plans into compact docs while preserving durable contracts. Use when: regular docs maintenance, collapse docs/plans/completed history, migrate plan outcomes into docs/specs or docs/design, clean up docs/PLANS.md links, enforce docs taxonomy (plans vs references).
Review entire repository and decide whether implementations should be documented in existing or new docs/specs files, then update docs/specs accordingly. Use when: repository-wide spec audit, contract drift checks, spec gap detection, docs/specs maintenance, adding action/CLI/API/file-format contracts.