メニュー
Playbook for capturing design alignment from /grill-me, generating issue specifications, and managing task boards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Playbook instructing agents how to dynamically formulate, design, bootstrap, and register new workspace skills when facing skill gaps.
Playbook for translating natural language requests about tasks, profiles, locking, and validation into CLI helper executions.
Playbook for writing safe database migrations, managing schema evolutions, executing reversible rollbacks, and avoiding table lock contention in enterprise environments.
Guidelines for CPU profiling, identifying database query bottlenecks (N+1 queries), diagnosing memory leaks, and optimizing resource execution speeds.
Guidelines for containerization (Dockerfile best practices), release versioning, blue-green deployment, feature flag rollouts, and post-deployment smoke verification.
Diagnostic and recovery playbook for resolving local git states, locked configuration files, broken workspace setups, and process deadlocks.
| name | task-management |
| description | Playbook for capturing design alignment from /grill-me, generating issue specifications, and managing task boards. |
Use this playbook immediately after a /grill-me design alignment session to capture decisions and scaffold tasks.
After aligning with the user on technical designs, the agent MUST capture the decisions into a new issue markdown file under .agents/issues/issue_[id].md.
Every design capture file must follow this schema:
---
id: issue-[number]
title: "Clear descriptive title"
status: open
assignee: agent-antigravity
milestone: "v3.4x"
created_at: [current-date]
---
# Design & Task Specification
## 1. Technical Decisions
- **Stack**: [Target languages/frameworks]
- **Architecture**: [Blueprints or design patterns applied]
- **Key Modules**: [Files to create or edit]
## 2. Implementation Subtasks
- [ ] Subtask A (e.g. Write tests)
- [ ] Subtask B (e.g. Write business logic)
- [ ] Subtask C (e.g. Validate output)
## 3. Acceptance Criteria
- [ ] Criterion 1 (e.g. Passes pre-commit checks)
- [ ] Criterion 2 (e.g. Tests cover all endpoints)
Once the issue file is written:
python3 .agents/scripts/sync.py to synchronize any links.board.md) is automatically synchronized with local issues when running ./helper.sh issue sync. You can also manually add/move the task if needed:
- [ ] [Title] (feat/issue-[number]) <!-- id: issue-[number] -->- [ ] issue-[number]) under the corresponding milestone version section in .agents/memory/milestones.md.Doing before starting work../helper.sh issue checkout issue-[number]). NEVER edit files or commit directly on the main or master branch.Note: Task statuses and checkbox states in board.md are automatically kept in sync with issue file statuses whenever issues are synchronized, checkout, or closed.