loaf

Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow guidance (workflow skills own their CLI contracts) or build internals.

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow guidance (workflow skills own their CLI contracts) or build internals.

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow guidance (workflow skills own their CLI contracts) or build internals.

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).

Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow ...

Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "pu...

Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifa...

Covers branching strategies, commit conventions, PR creation, and squash merge workflow. Use when creating branches, writing commits, creating or merging PRs, or managing git history. Provides patterns for collaborative git workflows. Not for code style (use foundations) or CI/CD pipelines (use infrastructure-management).

Reviews, verifies, and lands one pull request. Use when the user says "ship it," "merge this PR," "ready to merge," "land this branch," or asks for a final merge gate. Produces a reviewed, squash-merged PR and post-merge cleanup. Not for version bumps, tags, GitHub Releases, or install verification (use release).

Covers branching strategies, commit conventions, PR creation, and squash merge workflow. Use when creating branches, writing commits, creating or merging PRs, or managing git history. Provides patterns for collaborative git workflows. Not for code style (use foundations) or CI/CD pipelines (use infrastructure-management).

Reviews, verifies, and lands one pull request. Use when the user says "ship it," "merge this PR," "ready to merge," "land this branch," or asks for a final merge gate. Produces a reviewed, squash-merged PR and post-merge cleanup. Not for version bumps, tags, GitHub Releases, or install verification (use release).

Covers branching strategies, commit conventions, PR creation, and squash merge workflow. Use when creating branches, writing commits, creating or merging PRs, or managing git history. Provides patterns for collaborative git workflows. Not for code style (use foundations) or CI/CD pipelines (use infrastructure-management).

Reviews, verifies, and lands one pull request. Use when the user says "ship it," "merge this PR," "ready to merge," "land this branch," or asks for a final merge gate. Produces a reviewed, squash-merged PR and post-merge cleanup. Not for version bumps, tags, GitHub Releases, or install verification (use release).

Covers branching strategies, commit conventions, PR creation, and squash merge workflow. Use when creating branches, writing commits, creating or merging PRs, or managing git history. Provides patterns for collaborative git workflows. Not for code...

Reviews, verifies, and lands one pull request. Use when the user says "ship it," "merge this PR," "ready to merge," "land this branch," or asks for a final merge gate. Produces a reviewed, squash-merged PR and post-merge cleanup. Not for version b...

Creates Architecture Decision Records for architecturally significant decisions — choices that affect the system's structure, key quality attributes, dependencies, interfaces, or construction techniques, or that are difficult to reverse. Captures the rationale for a single such choice and its alternatives so future debate has the why preserved. Not for development patterns or implementation evidence (use /shape for SPECs), guiding principles (update ARCHITECTURE.md or VISION.md), workflow conventions (document in the owning skill), or local choices changeable in a single PR (log a `decision(scope)` entry to the project journal instead). The ADR log is append-only — when circumstances change, write a new ADR that supersedes the old one.

Bootstraps new or existing projects through intelligent state detection, structured interviews, and document population. Use when the user asks "how do I start a new project?", "set up Loaf," or "bootstrap my project." Produces populated project documents and setup recommendations. Not for shaping features (use shape) or brainstorming ideas (use brainstorm).

Conducts structured brainstorming with divergent thinking and trade-off analysis. Use when the user asks "help me think through this," "what are the options," or is exploring tradeoffs. Produces docs with sparks. Not for quick ideas or shaping.

Decomposes specifications into atomic tasks with dependencies and priorities. Use when the user asks "break this down" or "create tasks for this spec." Produces task files with estimates, dependencies, and acceptance criteria. Not for shaping ideas (use shape) or implementation work (use implement).

Convenes multi-agent council deliberations for decisions requiring diverse perspectives. Use when the user asks "call a council", "gather specialists", "get a council opinion", or "what do the experts think". Also activate when the user wants a structured debate between domain-specific viewpoints. Not for single-perspective research (use research) or architectural decisions that don't need multi-agent deliberation (use architecture).

Covers schema design, migrations, query optimization, indexing strategies, and normalization tradeoffs. Use when designing tables, writing migrations, optimizing queries, or planning index strategies. Provides patterns for database administration and development. Not for ORM usage in application code (use language-specific development skills) or infrastructure orchestration (use infrastructure-management).

Covers systematic debugging, hypothesis tracking, and flaky test investigation. Use when diagnosing failures, tracking hypotheses, or fixing flaky tests. Provides methodology for root cause analysis and issue resolution. Not for writing new tests (use development skills) or security analysis (use security-compliance).

Covers ADRs, API documentation, changelogs, documentation review, and Mermaid diagrams. Use when writing ADRs, documenting APIs, maintaining changelogs, reviewing documentation quality, or creating architecture diagrams. Not for inline code comments (use code style guides) or project READMEs (use project-specific conventions).

Establishes code quality, commit conventions, documentation standards, and security patterns. Use when writing or reviewing code, running checks, or setting up project standards. Covers naming, TDD, verification, and review workflows. Not for git workflow (use git-workflow), debugging (use debugging), or security audits (use security-compliance).

Covers idiomatic Go development: project structure, concurrency patterns, error handling, and testing. Use when writing Go services, CLIs, or libraries. Follows Effective Go principles and community conventions. Not for database schema design (use database-design) or infrastructure orchestration (use infrastructure-management).

Creates explicit context-transfer packets in .agents/handoffs/ for another agent, branch, task, or future conversation. Use when the user asks "handoff this," "prepare the next session," "write transfer context," or when work is being parked for later. Not for routine journal continuity (use orchestration) or an end-of-conversation checkpoint (use wrap). Produces a disposable handoff artifact that housekeeping deletes after confirmed deprecation.

Reviews and maintains agent artifacts in .agents/ — specs, plans, drafts, handoffs, councils, and reports. Use when the user asks "housekeeping," "clean up," or "tidy up .agents/." Provides hygiene recommendations, archives completed work, and ensures extracted knowledge is preserved. Not for strategic reflection (use reflect) or knowledge management (use knowledge-base).

Captures ideas into structured nuggets for later evaluation. Use when the user says "I have an idea" or "note this down." Also activate when a specific actionable concept crystallizes during conversation. For reviewing and processing the intake queue (sparks + raw ideas), use triage instead. Not for deep exploration (use brainstorm) or shaping (use shape).

Orchestrates implementation work through agent delegation and batch execution. Use for all implementation work — features, bug fixes, refactors, and code changes. Logs to the project journal and produces agent spawn plans and progress tracking. Not for shaping (use shape), breakdown (use breakdown), research, or review.