Outline Driven Development

Use when asked to review learning progress after a milestone. Not for engineering retrospectives, use engineering-retrospective. For agent-environment ones, use agent-environment-retrospective.

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

Use when a course needs numbered problem, solution, and explainer scaffolds. Not for a CLI or Next.js project scaffold: use scaffold-nextjs.

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

Use when reducing C/C++ compilation times with ccache, sccache, distcc, unity builds, precompiled headers, split DWARF, IWYU, or link time reduction.

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

Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.

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

Use when environment-dependent code, templates, or deployment configuration changes, or when runtime configuration is missing. Produces a bidirectionally reconciled environment-variable contract.

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

Use when the user explicitly asks to save, curate, or consolidate what was learned, or closes a meaningful knowledge-work session. Not for remote, publish, deploy, or irreversible 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 asked to summarize authored work over the last week or a named date range, commit range, or branch. Not for source or remote-system changes.

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

Use when the user explicitly says to save something to memory or scan this session for memories. Not for auditing memory: use memory-clean.

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

Use when asked to recover prior work and current status before resuming. Not for handoff snapshots: use handoff. Not for source or remote-system changes.

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

Use when the user and agent may hold different pictures of current state after a gap, sync request, or exposed stale claim. Not for persistence: use memory-update.

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.

Use when the user asks to view, export, or inspect a session transcript in a browser. Not for sharing a session: use session-share.

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 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 a project context-schema differs from the installed entry format. Not for remote, 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 the user requests a deep dive, exploratory analysis, or data analysis on BigQuery. Not for credential, publish, deploy, 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 the user asks to remove a session or note from recall, or to unforget or list exclusions. Not for remote, credential, publish, deploy, or irreversible changes.

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 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 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.