メニュー
ClanWorld project management — milestones, labels, hackathon deadlines, cut priorities. Read when triaging issues, opening PRs, or making scope decisions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Bootstrap procedure when an Elder starts a session with cleared context. Read order to rebuild situational awareness before responding to the first situation block.
Inheritance-test skill — confirms the elder agent's parent-walk picks up shared skills from `~/clan-world/.claude/skills/`. Stub for now; replaced when real elder skill set lands.
Framework for what to consolidate to memory before a context reset. Triggered when the runner injects a "final tick warning." YOU decide what's worth carrying forward — this skill gives you the framework, not a checklist.
Strategy for monitoring market for arbitrage opportunities and queuing scheduled buys/sells when spreads widen. Use when you have a worker free and your strategy seed favors trader behavior.
Read the current Unicorn Town market state — token pair prices, recent trade history, scheduled-action queue depth. Use when sizing up a market action or deciding whether to wait a tick.
Execute an immediate (this-heartbeat) market sell of a token your clan holds. Use when you need gold THIS tick to act on something else (e.g. mission with high gold cost, walls upgrade) and can't wait for a scheduled order.
| name | clan-world-pm |
| description | ClanWorld project management — milestones, labels, hackathon deadlines, cut priorities. Read when triaging issues, opening PRs, or making scope decisions. |
Just-in-time reference for the orchestrator and any PM-style agent working in this repo. Heavier reference (decision rationale, demo strategy) lives in docs/reference/prize-strategy.md.
| Submission 1 | Submission 2 | |
|---|---|---|
| Deadline | 2026-04-26 14:00 ET (today) | 2026-05-05 |
| Track | World mini app hackathon | OpenAgents Track 2 (iNFT transfer demo) |
| Chain | World Chain Sepolia | Base Sepolia |
| Heartbeat | Foundry shell loop, 20s ticks | KeeperHub workflow, 60s ticks |
| Demo punchline | 8 demo moments running inside World App | clan iNFT mint → mid-game transfer → memory continuity |
Nine numbered milestones spanning both submissions:
| # | Name | Description |
|---|---|---|
| M0 | Foundation | Wave 0 scaffold + adapter interfaces + docs (Issue #1) |
| M1 | Core engine | IClanWorld impl + Foundry deploy + first heartbeat tx |
| M2 | S1 Integration | Convex schema + frontend wiring + 4 Elders + orchestrator |
| M3 | S1 Polish | Whisper UI + region polygon visuals + World mini app wrapper |
| M4 | S1 Shipped | Demo recording + submission upload + tag s1-v0.1.0 |
| M5 | S2 Master Plan | Submission 2 master spec written; KeeperHub + 0G + AXL integration plan locked |
| M6 | S2 Integration | Base Sepolia redeploy + KeeperHub + 0G Storage KV + ERC-7857 iNFT minted |
| M7 | Track 2 Demo | Clan iNFT transfer flow with key handover + memory continuity verified |
| M8 | S2 Shipped | Demo recording + submission upload + tag s2-v0.1.0 |
Issues should reference exactly one milestone. PRs auto-tick the milestone via Closes #N.
Five axes; one value per axis per issue.
| Axis | Values |
|---|---|
track: | s1-world, s2-openagents, cross-cutting |
priority: | p0-blocker, p1-must-fix, p2-should, p3-nice |
status: | triage, ready, in-progress, blocked, review, done |
type: | feat, bug, chore, docs, refactor, infra |
scope: | web, server, orchestrator, contracts, agents, shared, ops, cross |
Defaults on issue creation: status:triage, priority:p2-should. Promote to priority:p1-must-fix only if it blocks a milestone.
Time pressure is real. If we're behind at a runtime gate (H3 or H5 in BUILD_PLAN.md), cut in this order.
IClanWorld deployed on World Chain Sepolia.heartbeat() tx on testnet with a public tx hash.docs/planning/V1/01 Blockchain Game Spec/clanworld_v1_implementation_profile.md §8.feat/issue-N-short-desc off dev.type(scope): desc (#N).Closes #N.docs/conventions/gitflow.md, docs/conventions/pr-review.md.If scope ambiguity is blocking work, post a comment on the relevant issue tagging the orchestrator. Do NOT silently expand or shrink scope. The orchestrator owns scope decisions per ~/claudes-world policy.