Outline Driven Development

Use when the user runs /toolchain-health and wants a trustworthy green/yellow/red verdict on the installed toolchain with ranked repairs. Not for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.

The English summary is being prepared. Showing the original description.

Use when repo content crosses into working context or synthesized knowledge. Flags injections and blocks derived instructions. Not for tasks requiring source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when work reaches a session boundary or the user asks to hand off, delegate, or get a clipboard-ready prompt. Mode brief packages continuity; mode prompt builds the delegation prompt.

The English summary is being prepared. Showing the original description.

Use when a user wants to record why one world won over the others, as a decision-diary entry. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when the user asks to beam, publish, or share the current local coding session to an authenticated remote receiver. Not for viewing a transcript locally: use session-viewer.

The English summary is being prepared. Showing the original description.

Use when a human-curated dbt model index must guide BigQuery SQL for a warehouse question. Not for discovering undocumented models or executing warehouse changes.

The English summary is being prepared. Showing the original description.

Use when the user asks to sanitize memory for sharing, redact PII, or scan memory for credentials. Not for auditing memory: use memory-clean.

The English summary is being prepared. Showing the original description.

Use when adding telemetry, composing an observability surface, reviewing alerts, shipping a production feature, or diagnosing a production issue. Not for live failures, profiling, or launch runbooks.

The English summary is being prepared. Showing the original description.

Use when an existing repository needs its unexplained rationale recovered into topic files. Don't use for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.

The English summary is being prepared. Showing the original description.

Use when a user requests the reasoning behind one matched session by query or handle. Not for peer transfer: use history-sync. Not for store registration: use history-source-registry.

The English summary is being prepared. Showing the original description.

Use when asked to find duplication, check consistency, establish or repair SSOT, consolidate facts, or when the user says "consolidate this" or "ssotize this". Not for remote or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when the user requests memory transfer to or from a named peer. Not for recalling a session: use history-recall. Not for store registration: use history-source-registry.

The English summary is being prepared. Showing the original description.

Use when departing knowledge must enter project topic files through a narration-first interview. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.

The English summary is being prepared. Showing the original description.

Use when the user asks to rank deployment platforms and stacks against their product with quantitative trade-offs. Not for source or remote mutation.

The English summary is being prepared. Showing the original description.

Use when skill or knowledge activation is unreliable, or setup reaches activation reliability. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when writing, reviewing, or generating Terraform HCL that must pass fmt and validate. Not for module authoring, state operations, `terraform apply`, or remote state.

The English summary is being prepared. Showing the original description.

Use when contradictions, revisit conditions, or duplicates appear in knowledge entries. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when project documentation needs a layout or a knowledge item needs one home. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a human asks to audit memory, find stale or duplicate memories, or needs tidy's ICM-state audit. Not for writing new memories: use memory-update.

The English summary is being prepared. Showing the original description.

Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.

The English summary is being prepared. Showing the original description.

Use when a knowledge artifact needs review before sharing or execution. Not for source or remote-system changes.

The English summary is being prepared. Showing the original description.