aming-claw

Single Aming Claw skill entrypoint. Use this first for Aming Claw governance, backlog, graph, runtime, worker, QA, dashboard, MCP, install/start/bootstrap, or dogfood work; prefer the MCP onboard_route_guide tool before choosing a role or successor contract.

Public demo for Backlog Duplicate: a new requirement overlaps existing backlog work, and the observer asks whether to merge, supersede, or keep it separate. Use when a user asks to run, preview, or collect duplicate backlog evidence with the current Claude Code or Codex observer session.

Public demo for Docs Drift: a feature changes but documentation is stale, and the drift state is surfaced before a second doc fix. Use when a user asks to run, preview, or collect evidence for docs drift with the current Claude Code or Codex observer session.

Public HN challenge entrypoint for Aming Claw. Use when a user asks to run, preview, present, or collect evidence for the multi-agent challenge: one observer coordinates multiple commit-bound workers, records a failed or interrupted worker, replays it from the same contract lineage, reconciles the target graph, and writes an audit self-review.

HN demo case for the fear that code changes leave docs, tests, and config stale after implementation. Guides evidence collection for Asset Inbox, binding state, Baseline and Possible drift, Review Queue, impact scope, and review boundaries.

HN demo case for the fear that AI does not understand project structure and duplicates work. Guides evidence collection for graph-first discovery, backlog contract, target file fence, and acceptance criteria before implementation.

HN demo case for the fear that AI and subagents are black boxes during implementation. Guides evidence collection for timeline DAG, observer and subagent lanes, dispatch gate, evidence inspector, isolated worktrees, and append-only contract evidence.

Guided operator for the Aming Claw HN multi-agent challenge demo. Use when a user asks to run, preview, present, or collect evidence for the HN demo showing one observer coordinating multiple commit-bound workers, failed/interrupted worker replay, graph traces, reconcile, and audit self-review.

Explicit Aming Claw onboarding and launcher entry. Use for `/aming-claw:aming-claw-launcher`, "aming-claw launcher", "onboard me to Aming Claw", "start/open dashboard/status", install-and-start requests, fresh project registration, or any onboarding question. Defer graph, backlog, semantic, manual-fix, or chain implementation work to `/aming-claw:aming-claw` after this state machine reaches the fixed first-value steps.

Use when a user wants to capture raw requirements, keep talking without dispatching work, review a batch of captured requirements, or promote confirmed requirements into Aming Claw backlog rows from the Project Inbox.

Use when working in the Aming Claw repo or any governance, dashboard, MCP, backlog, graph, semantic reconcile, scope/full reconcile, chain/executor advanced ops, or manual-fix/observer-hotfix task. Enforces graph-first discovery, backlog/MF tracking before mutations, MCP-first operations, Chain trailers on commits, and post-commit runtime/graph checks.

Use when reviewing user-facing Aming Claw flows against the bundled ue_audit.v1 contract, especially ordinary non-technical builder flows where request and state visibility matter.

Public demo for Vibe Queue: keep talking while agents work. Use when a user asks to run, preview, or collect evidence for a mid-implementation requirement being handled by the current Claude Code or Codex observer session.