knowns

Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.

Use when you need to understand existing code, find patterns, search project knowledge, use web research for external/current facts, or explore a large codebase before implementation

Use when committing code changes with proper conventional commit format and verification

Use when working with Knowns documentation - viewing, searching, creating, or updating docs

Use when extracting reusable patterns, decisions, failures, or knowledge into documentation

Use only when the user explicitly wants the legacy no-review-gates pipeline for an approved spec; prefer kn-flow for normal spec orchestration

Use when implementing a task - follow the plan, check ACs, track progress

Use at the start of a new session to read project docs, understand context, and see current state

Use when creating an implementation plan for a task

Use when reviewing implemented code before committing — multi-perspective review with severity-based findings

Use when creating a specification document for a feature (SDD workflow)

Use when generating code from templates - list, run, or create templates

Use when running SDD verification and coverage reporting

Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn