메뉴
Break a VFloat PRD, plan, or spec into AFK workflow issue files under .scratch. Use when creating implementation tickets, vertical slices, or issue-worker tasks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when creating, updating, reviewing, or syncing VFloat documentation in docs/api or docs/guide, especially after source changes in src/composables/ or when the user asks for VFloat API pages, guides, tutorials, doc fixes, or docs review feedback even if they do not name the docs folders directly.
Coordinate VFloat's markdown-based AFK issue workflow. Use when creating, assigning, implementing, reviewing, committing, or monitoring .scratch PRD and issue files across Codex or other markdown-capable agents.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Prepare final validation and Conventional Commit proposals for completed VFloat AFK workflow work. Use when all feature issues are completed or a PRD is ready-to-commit.
Review one VFloat AFK workflow issue after implementation. Use when an issue is ready-for-review and needs diff review, acceptance validation, follow-up issue creation, or completion.
| name | to-issues |
| description | Break a VFloat PRD, plan, or spec into AFK workflow issue files under .scratch. Use when creating implementation tickets, vertical slices, or issue-worker tasks. |
Break a PRD or plan into independently grabbable vertical slices for the AFK issue loop.
Read before writing:
AGENTS.md.agents/workflows/afk-issue-loop.md.agents/issue-tracker.md.agents/triage-labels.mdIssues must be understandable by any markdown-capable agent. Avoid Codex-only language in issue bodies.
If the user passes a PRD, issue number, or path, read it fully. If the source is conversation context, explore the codebase enough to use VFloat terminology and respect relevant ADRs.
Break the plan into tracer-bullet issues. Each issue should deliver a narrow, complete behavior path with its own acceptance criteria and validation expectations.
Classify each slice:
ready-for-agent after triage.ready-for-human because it needs human judgment,
design approval, credentials, or manual verification.Present the draft breakdown with title, type, blockers, and covered user stories. Iterate until approved.
Create files at .scratch/<feature-slug>/issues/<NN>-<slug>.md in dependency
order. New issues start as Status: needs-triage, even when they look AFK, so
triage can verify readiness and add the final agent brief.
Status: needs-triage
Category: enhancement
Assignee: unassigned
Branch/worktree: not-started
Parent: .scratch/<feature-slug>/PRD.md
Blocked by: None
# <Issue Title>
## What to build
A concise description of the end-to-end behavior this slice delivers.
## Acceptance criteria
- [ ] Specific, testable criterion 1
- [ ] Specific, testable criterion 2
- [ ] Specific, testable criterion 3
## Agent Brief
To be completed by triage before moving to `ready-for-agent`.
## Work Log
- Not started.
## Validation Log
- Not run.
## Review Notes
- Not reviewed.
## Comments
Do not close or mark the parent PRD complete while publishing issues.