core

Plugin core in eugenelim/agent-ready-repo. Commands read from the repo's manifest — today.

Skills (21)

• adapt-to-project

  Use this skill to diagnose and improve an adopter repository's agent guidance or to walk through the four classes of post-install change (substitution, .upstream companion merges, discovery + restructuring, within-layout consolidation). Repository anchoring is marker-independent and read-only by def

• author-brief

  Deprecated compatibility alias for author-delivery-brief create. Use only when an older caller explicitly invokes author-brief.

• author-delivery-brief

  Use with an explicit create or continue mode to author a Draft delivery brief from a coherent multi-slice or cross-repository outcome, or to review an existing repository brief for Ready and select confirmed delivery slices.

• bug-fix

  Use this skill when the user wants to diagnose or fix a deviation between current and intended behavior in existing code -- including requests to find the root cause, explain a CI-only failure, investigate intermittent or flaky behavior, or contain and diagnose a production incident. Triggers on "fi

• close-work

  Use when completed, abandoned, or superseded delivery work needs closeout, durable-context verification, initiative reconciliation, pause handling, or a safe immediate-disposition preview.

• contract-acquisition

  Acquire a platform's or library's real contract from its own toolchain oracles before authoring against an unfamiliar one — infrastructure, a CLI invocation, code on a managed runtime, or code against an unfamiliar framework or third-party library whose contract you don't hold. Triggers on "deploy t

• explain-diff

  Use this skill when a user asks for a self-contained explanation of how a local code diff, branch, commit, or pull-request representation works. It traces the changed code and nearby tests, designs a work-specific offline HTML lesson, publishes it through the bundled standard-library publisher, and

• init-project

  Use this skill to turn an idea into a structured new repo. It runs a trigger gate (throwaways and single scripts skip it), a value gate over fed-in discovery, records a foundation (an ADR plus a reference.md golden path), authors a walking-skeleton spec via new-spec and hands the build to work-loop,

• intake-intent

  Use when a raw or admitted request should become a minimum repository intent for later shaping, without creating an RFC, delivery brief, spec, or executable queue item.

• navigate-intents

  Use this skill when asked to look up, trace, explore, or summarise product intents, to find outstanding work placed under its parent intent, or to export them as offline HTML. Triggers on phrases like "show me intent:my-slug", "which intents are accepted", "trace the parent of this intent", "find ou

• new-spec

  Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for

• operational-safety

  Progressive-disclosure operational-safety-depth modules for the work-loop. Holds failure-mode-keyed checklists the quality-engineer reviewer reasons from (state-and-idempotency, blast-radius, environment-isolation, cost-and-teardown, drift-and-rollback, observability-and-smoke), plus cloud-implement

• project-knowledge

  Use this skill to capture, distill, or enquire over project knowledge through one progressive mode, or to list unadmitted knowledge candidates from delivery review failures. Capture admits one strict observation contract; distill reconciles pending observations; enquire reads committed active topics

• receive-brief

  Deprecated compatibility alias for author-delivery-brief continue. Use only when an older caller explicitly invokes receive-brief.

• repository-exploration

  Use this skill when a workflow step or a user needs bounded, attributed repository evidence to settle a pending decision — which files a plan must touch, whether a rename or removal is safe, where a bad value enters before a fix, or whether a fix reaches a live code path. It owns that inquiry for th

• repository-grounding

  Use this skill to answer "what already governs these paths?" before writing a spec, plan, or implementation. Probes the paths a change will touch and reports governing files, references, phrase pins, gates, co-change partners, and dead links — selected by stage. Use it at discovery to orient before

• security-checklists-reference

  Route into the compiled OKF bundle `security-checklists` using generated indexes.

• security-checklists

  Progressive-disclosure security-depth modules for the security-reviewer. Holds boundary-keyed checklists (access-control, authn-session, injection, path-and-file, secrets-and-crypto, outbound-ssrf, supply-chain, config-misconfig, exceptional-conditions, llm-agent, agentic-skills) as references/, eac

• work-intake

  Use for a raw or ambiguous work request, source acquisition or refresh, or generic intake-safety handling. Explicit status, artifact, skill, product-shaping, architecture-design, and defect requests route directly to their owners.

• work-loop

  Use when implementing or resuming a non-trivial repository change: a feature, a fix whose cause is established (use `bug-fix` first to diagnose a defect whose cause is not), refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system c

• workspace-status

  Use this skill to repair or migrate the entries `workspace.toml` still holds onto their own artifacts, with `repair-plan` to preview and `repair-apply` to write. Triggers on "run repair-plan", "apply the workspace repair plan", "fix queue drift", "migrate workspace.toml", "move captured items into f