Turns the current session's context into a self-contained, execution-ready brief that a fresh agent session or a spawned subagent can run without seeing this conversation. Use this whenever the user wants to move work to another agent or a new session and wants the instructions written down first. Trigger on phrases…
Use to answer questions about agent sessions across every project at once, and to act on one where the harness allows it. Reports which sessions exist, which are running, what each cost, which skills were used, and what failed, by reading the local observatory store rather than one transcript at a time. Where the…
Writes new Markdown documentation for the repository it is used in, grounded in the actual code. Handles READMEs (technical or for non-technical readers), architecture docs with Mermaid diagrams, setup and deployment guides, contributing guides, design docs, and architecture decision records. Use this whenever the…
Updates and revises existing Markdown documentation in place, without flattening its voice or rewriting more than asked. Reconciles a doc with the current code or project state, fixes cross-document links and references after files or folders have moved, keeps a set of docs internally consistent. Use this whenever the…
Use when code has moved and the documentation may not have, or when a documentation set needs auditing for stale claims. Detects documentation drift by checking prose claims against repository facts, classifies every document as current-state (correctable), contract (report-only, human-owned) or ledger (skipped), and…
Delegate a batch of independent, already-scoped task files (bugs, chores, small features) to parallel isolated agents, each sandboxed in its own git worktree, with a mandatory independent verification pass before anything is treated as mergeable. Use this whenever asked to "fix these bugs", "work through the backlog"…
Review a code change against an explicit house rubric and severities, and produce a structured, severity-ranked markdown review, without editing or committing anything. Determines the review range (the current branch against its merge-base with the default branch, with a working-tree fallback), applies the…
Packages the current state of a project into a handoff for a person: a business partner, a client, or a team member. Produces a document or a short message, in plain language, tuned to the reader, with internals and costs redacted when the reader is a client. Use this whenever the user wants to bring a person up to…
Scaffold a portable, agent-optimized spec-driven work-tracking system into the current repository: AGENTS.md (global rules + agent reading protocol), a .tasks/ directory of atomic task files, and (by tier) ROADMAP.md, CHANGELOG.md, a validate.py checker, and thin CLAUDE.md/Cursor/Copilot pointers. Choose a footprint…
Author one or more atomic, agent-ready task files for the .tasks/ work-tracking system, at a gold-standard bar. Turns a rough idea, a bug report, or a ROADMAP.md Feature into task files with honest touchedfiles, a real parent up-link, resolved dependson, and a mechanically-verifiable acceptance command, then…
Draft a pull request description and a matching changelog entry from a branch's diff, in the target repo's own changelog format, without touching GitHub. Determines the PR's commit range (the current branch against its merge-base with the default branch), surveys what changed, then produces a structured PR body plus a…
Safely consolidate one or more isolated git worktrees (for example left behind by parallel background agents, or from the fix-batch skill) into the main working tree, without committing or merging blindly. Use whenever asked to "reconcile the worktrees", "merge these agent branches", "bring the worktree changes back…
Decide how much review a change has earned, before reviewing it. Selects quick, standard, or deep from stated signals (reviewable changed lines, directory spread, trust-boundary risk flags, blast radius, documentation-only scope), reports the signal table and the rule that fired, then runs house-review at the selected…
Use when turning a raw idea, feature request, or bug into a persistent behavioral spec before any tasks or code. Drafts a scenario-based spec (problem, goals, non-goals, constraints, Given/When/Then scenarios with stable S-NNN ids, proposed surface, open questions), composes the spec-quality lens to self-check and…
Use when closing a spec-driven feature or issue, or auditing whether an implementation actually matches its spec. Given a spec path, emits a section-by-section conformance matrix mapping every scenario and proposed surface element to conformed (with file:line or test evidence), diverged (what, why, and both sides), or…
Use before implementation when a spec and its task decomposition must be checked for coding readiness. Applies a deterministic go/no-go gate for missing inputs, unresolved spec blockers, incomplete ordered task lists, spec-task contradictions, task-to-scenario traceability, scenario-to-test layer mapping…
Use after an implementation to derive runnable tests from an approved spec's Given/When/Then scenarios and a task's acceptance criteria, one faithful test per scenario tagged with its S-NNN id. Stops rather than deriving tests from a spec whose status is not approved. Discovers and matches the repo's existing test…
Use when creating, modifying, reviewing, or deciding whether to add tests, fixtures, mocks, integration tests, end-to-end tests, smoke tests, or test plans in any codebase or language, including regression tests for bug fixes. Chooses the test layer and oracle: guides agents to pick the right test layer, avoid…
Use before reconciling or landing an implementation to independently verify it against its approved spec and its task's acceptance criteria. Runs the declared verification commands and records each exact outcome, composes the spec-conformance lens so a contract divergence fails the run even when every command passes…
AGENTS.md instructions for hams-ollo/zen-agent-skills, covering agents.md: rules for the zen agent skills repository, 0. agent reading protocol (read this first), 1. what this repository is, 2. layout and 3. work altitude model and lifecycle.
Claude Code instructions for hams-ollo/zen-agent-skills: Claude Code loads this file automatically, so it stays in place as a redirect. The canonical rules for every AI agent working in this repository live in AGENTS.md. Read that file, not this one.