メニュー
Use when implementing features or fixes that correspond to .tasks checklists. Open the relevant .tasks file (e.g. 01-pea-core, 02-windows), implement unchecked items, and mark completed items with [x]. Run fully autonomously: no confirmation for build, test, commit, or push.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when making architectural decisions, adding components, or understanding how PeaPod's pieces fit together. Provides context on the protocol design, component boundaries, and data flow to help agents make correct design choices.
Use when finishing a chunk of work or when the user asks to commit or to update Cursor context. Commit and push with a clear message; optionally add or update a rule, skill, or subagent in .cursor. Execute without prompting (autonomous mode).
Use when building, testing, or verifying pea-core or the workspace. Run cargo build and cargo test for pea-core from repo root; fix compilation or test failures. Execute without asking for confirmation (autonomous mode).
Use when working on Windows, Android, Linux, iOS, or macOS protocol implementations (pea-windows, pea-android, etc.). Follow the corresponding .tasks file (02–06); ensure wire format and discovery match pea-core and .tasks/07.
| name | peapod-tasks |
| description | Use when implementing features or fixes that correspond to .tasks checklists. Open the relevant .tasks file (e.g. 01-pea-core, 02-windows), implement unchecked items, and mark completed items with [x]. Run fully autonomously: no confirmation for build, test, commit, or push. |
Autonomous: Do not ask for confirmation. Execute each task item, run build/test if Rust changed, commit and push, then continue to the next item. Hooks auto-allow shell commands and auto-continue the conversation.
When the user asks to implement work that maps to the task breakdown:
Identify the task file from .tasks/README.md. Follow the recommended order: 00 → 01 → 07 → 02 & 03 → 04, 05, 06 → 08, 09.
Open the relevant .tasks file (e.g. .tasks/01-pea-core.md for core work, .tasks/02-windows.md for Windows).
Implement in dependency order: Complete parent tasks before children where the checklist implies it. Do not skip items that block others.
Update checklists: As you complete each item, change - [ ] to - [x] in the corresponding .tasks file. Only mark done when the work is implemented and verified (e.g. build/tests pass).
Add sub-tasks only when needed: If you discover a necessary step not in the list, add it under the appropriate ## or ### so the hierarchy stays clear.
Evolve .tasks: When new requirements emerge, add tasks to the appropriate file; when findings arise (design decisions, root causes, gotchas), add notes inline or in a ## Notes section at the end of the file. For session behavior (e.g. continuing from the next unchecked item when no specific goal is set), follow the task-continuity rule in .cursor/rules/task-continuity.mdc.
