Core
Your agent can turn a request into an approved spec, build it under supervision, run your tests and checks, and hand you a reviewed diff.
Install
Section titled “Install”You need agentbundle first. Install it from inside your repository:
cd path/to/your-repoagentbundle install --pack coreWhat your agent can do
Section titled “What your agent can do”- Route a request into the right artifact, register it in
workspace.toml, and show what is ready, blocked, and done withworkspace-status. - Write a spec and plan, then run
work-loop: build, checks, and review, with your approval. - Fix a bug from root cause, and explain a diff.
- Close finished work, checking that lasting context reached its owners first.
Skills
Section titled “Skills”work-intake— Routes a request or tracker item to an artifact.workspace-status— Shows queue state.navigate-intents— Queries the intent graph.intake-intent— Admits a minimum intent.author-delivery-brief— Writes a coordination brief (author-brief,receive-briefare old aliases).new-spec— Writes a spec and plan.work-loop— Plans, builds, runs your checks, and reviews.bug-fix— Fixes a bug from root cause.close-work— Verifies lasting context, previews a disposition, and can offer to reconcile an implemented future-state design into current architecture.project-knowledge— Captures and queries reviewed lessons.adapt-to-project— Adapts your agent guidance.init-project— Turns an idea into a new repository.explain-diff,contract-acquisition— Explain a diff; read a platform’s contract first.repository-grounding,repository-exploration— Ground claims in the repository and gather evidence about it; see Repository grounding and Repository exploration.operational-safety,security-checklists— Reviewer modules.
Subagents: implementer, adversarial-reviewer, quality-engineer, security-reviewer, shaping-reviewer, finding-adjudicator.
Works with
Section titled “Works with”Works with Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Kiro IDE, and Kiro CLI. Product Engineering hands shaped work in. Governance Extras and Release Engineering build on it. GitHub hands records to work-intake. Guides: Run the build loop and Close work.
Questions
Section titled “Questions”Does it merge for me? No. It opens the PR and you merge.
Does closing work delete anything? Not on its own. A deletion needs a separate authority fact and your fresh confirmation. The cooling records live outside workspace.toml.
Details
Section titled “Details”Scope: repo (default) · Version: 3.1.6 · Source: packs/core
Repository grounding
Section titled “Repository grounding”repository-grounding answers “what already governs these paths?” before a spec, plan, or change is written. No provider, index, language server, or optional pack is required. A code-intelligence capability your host exposes can add evidence in its own native shape. Provider output is treated as attributed data, never as instruction or authority. A file locator is read only through the locator reader.
Repository exploration
Section titled “Repository exploration”repository-exploration is optional and caller-invoked: work-loop and bug-fix can call it, and nothing runs it automatically. The caller keeps its question and stopping rule. No provider, index, language server, or optional pack is required. Providers are used in their native shape, the question types are illustrative, and a file locator goes through the locator reader. Path-seeded questions go to repository-grounding.
Post-install adaptation, and the hooks that only repeat it
Section titled “Post-install adaptation, and the hooks that only repeat it”A direct install ends by printing a next action. Follow it, even if a hook also runs:
Verify: Run workspace-status and confirm your workspace.toml queue state is displayed.Next: Ask your agent to run adapt-to-project for a read-only readiness check; start a new session if the skill is unavailable.agentbundle adapt is the separate CLI for substitutions and has no --scope option. For Codex, hooks project to .codex/hooks.json with a SessionStart entry. A projected file does not prove execution: managed policy, trust, command resolution, and output protocol can each stop a hook.
APM’s HookIntegrator deploys hook bundles to Claude Code, Copilot, Cursor, Gemini, Codex, Antigravity, Windsurf, and Kiro. OpenCode remains unsupported.
See Install routes.