菜单
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.
用 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.
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.
Implement one VFloat .scratch issue from the AFK workflow. Use when an agent is assigned a ready-for-agent issue, must update Work Log and Validation Log, and should move it to ready-for-review.
| name | agent-workflow |
| description | 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. |
Use this skill whenever work moves through the AFK issue loop. It is the shared orchestration layer for planner, coordinator, worker, reviewer, and committer agents.
Read .agents/workflows/afk-issue-loop.md before taking action. The issue file
in .scratch/ owns current state. Agent memory, chat summaries, and background
thread titles are hints only.
Also read:
AGENTS.md for project conventions..agents/issue-tracker.md for local markdown issue layout..agents/triage-labels.md for status vocabulary..agents/rules/commit-message.md before commit proposal work.When acting as coordinator:
.scratch/**/issues/*.md.ready-for-agent issues.Status: in-progress, Assignee,
and Branch/worktree.ready-for-review.ready-to-commit only after every child issue is
completed.When prompting a worker, include:
Read AGENTS.md and .agents/workflows/afk-issue-loop.md.
Implement exactly one issue: <issue-path>.
Read the parent PRD before editing source.
Update Work Log and Validation Log in the issue.
Set Status: ready-for-review only when acceptance criteria are met.
Preserve unrelated worktree changes.
When prompting a reviewer, include:
Read AGENTS.md and .agents/workflows/afk-issue-loop.md.
Review exactly one issue: <issue-path>.
Compare the diff, acceptance criteria, and Validation Log.
If acceptable, set Status: completed and append Review Notes.
If not, create follow-up issue files with Status: ready-for-agent and set the original issue to review-blocked.
When prompting a committer, include:
Read AGENTS.md, .agents/workflows/afk-issue-loop.md, and .agents/rules/commit-message.md.
Prepare commit proposals for completed work under <feature-path>.
Run final validation or record why it cannot run.
Group changes into logical Conventional Commit messages.
Do not stage or commit without explicit human approval.
Status: ready-for-human.