domains / families / business / project-state-governor

project-state-governor

authentic

Govern evidence-backed canonical project state across sessions, branches, reviews, and research cycles without inventing product intent.

When to use

• Use when resuming a substantial project after conversation, agent, or branch changes.
• Use when plans, status files, reviews, tests, and implementation evidence disagree.
• Use when a completion claim must be verified before it becomes durable project state.
• Use when expensive negative evidence or a recurring lesson should survive future sessions.
• Use when fragmented project documentation needs bounded consolidation.

When not to use

• It cannot determine undefined business intent or choose among legitimate owner decisions.
• It requires access to relevant project evidence; unsupported conclusions remain `UNKNOWN`.
• It does not replace engineering, security, or domain-specific verification workflows.
• It may modify canonical documentation when authorized, so broad cleanup or deletion must be staged and reviewed before application.

Skill page

Source