Help us improve
Share bugs, ideas, or general feedback.
From aming-claw
Guides evidence collection using graph-first discovery and backlog contracts to prevent AI from duplicating work. Demonstrates synthetic demo data setup for a bounded, auditable start condition.
npx claudepluginhub amingclawdev/aming-claw --plugin aming-clawHow this skill is triggered — by the user, by Claude, or both
Slash command
/aming-claw:aming-claw-hn-demo-before-workThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before any response that uses this skill, in this exact order:
Governs Aming Claw projects with graph-first discovery, backlog tracking, and MCP operations. Enforces commit trailers and post-commit checks for governance.
Initiates tasks by interviewing user for requirements, setting up git-wt worktrees or branches, checking tools like direnv/dotenvx, and creating plans for review.
Routes sessions in long-task projects to the correct phase skill by checking files like bugfix-request.json, feature-list.json, design docs, and codebase state.
Share bugs, ideas, or general feedback.
Before any response that uses this skill, in this exact order:
ListMcpResourcesTool() ReadMcpResourceTool(uri="aming-claw://current-context") ReadMcpResourceTool(uri="aming-claw://skill") ReadMcpResourceTool(uri="aming-claw://graph-first")
current-context anchors project_id, governance URLs, and 3 guardrails. skill is the operating contract (Start Sequence, Observer Operating Modes). graph-first has copy-pasteable graph_query payload examples.
Common failures when these are skipped:
Show how Aming Claw turns "the AI will grep blindly and duplicate work" into a bounded, auditable start condition.
AI does not understand the project structure, misses existing modules, and creates duplicate work.
backlog_list or governance API
response for the proposed work title/files before backlog_upsert, recorded
exactly with count, bugs, and request_id.If task_timeline_list / backlog_list returns empty for the demo project, you are CREATING demo data, not reading existing data. Mandatory rules:
DO NOT call task_create with type=pm/dev/test/qa/merge. That is the chain path. V1 default is observer-led mf_parallel.v1.
Write parallel_contract into backlog.chain_trigger_json via backlog_upsert. workers[] is an array; for parallel work include multiple workers with DISJOINT owned_files.
Tie every task_timeline_append to the same mf_id (MF-). Per-worker events use the worker's task_id; observer events can use parent_task_id.
For each mf_sub graph_query: query_source="mf_subagent" + the worker's task_id, parent_task_id, worker_role="mf_sub", fence_token as top-level params.
Capture the returned trace_id and write into payload.graph_query_trace_ids in the timeline event. NEVER fabricate trace_id strings -- anyone can GET /api/graph-governance//query-traces/<trace_id> to verify.
mf_type=chain_rescue in mf_timeline_precheck output is the MVP MF storage bucket label, not an error. See aming-claw://mf-sop.
This subskill inherits the observer-mode operator role, mode boundaries, and
acceptance criteria from the umbrella aming-claw-hn-demo skill loaded by the
Skill tool.
Do not invent an aming-claw://skill-hn-demo MCP resource.
This subskill covers only Before Work operator steps for graph-first discovery, backlog duplicate/overlap probing, backlog contract evidence, target fence evidence, and acceptance criteria. Use Design Alignment by default; enter Execution Supervisor only when the umbrella mode gate is explicitly satisfied.
aming-claw start; do not start it silently.graph_status or the dashboard.count, bugs, and request_id.Before-work evidence
- Fear: project structure misunderstanding and duplicate work
- Graph: <snapshot/link/screenshot/node evidence>
- Backlog duplicate/overlap probe: <exact governance response/request_id>
- Backlog contract: <bug id/link/screenshot>
- Fence: <branch/worktree/files/base commit>
- Acceptance criteria: <summary or link>
- Architecture reason: commit-bound graph + graph-first discovery + backlog contract
- Limitations: <none/offline dashboard/manual screenshot/etc>