Groundwork

Shape raw or ambiguous product/engineering intent into compact PRD/spec before slicing, agent delegation, or implementation. Includes raw ideas asking to split issues for agents. Not for rewrites, accepted tasks, implementation, verification, handoff, dispatch, or wiki.

Package-only routing for accepted ready tasks or large read-only multi-perspective audit routing: model/profile, matrix, Dispatch Package, result expectations. Not for execution, worktrees, subagents, branch mutation, readiness, raw tasks, or doing the audit itself.

Classify readiness, blockers, severity, AFK/HITL, lifecycle-state need, closeout, or whether incomplete information should be blocked or handed off. Not for shaping, slicing, code edits, planning, verification reports, dispatch packages, or wiki.

Use for evidence-sufficiency questions: "验证通过吗?", diff summary sufficiency, whether self-review can count as clean review, readiness/release/UAT/runtime support, UI evidence, and evidence packages. Not for code edits, raw requirements, slicing, or conformance review without evidence/readiness judgment.

Slice accepted PRD/spec/plan into vertical task drafts with acceptance, blockers, state, and verification expectations. Not for raw/ambiguous requirements, raw ideas asking to split issues for agents, incomplete-info blocked/handoff judgment, implementation, readiness, or one-off planning.

Bug fixes, patch/code edits, "修 bug", "直接 patch", "改代码", confirmed fixes, diagnose-before-edit, blocked implementation when source truth is missing, or read-only implementation conformance review. Not for raw requirements, slicing, readiness/UAT/release verification, handoff, or dispatch.

Preserve compact continuation state across sessions, agents, review packages, or future work. Not for one-offs, full PRD/diff/log copies, code edits, readiness, dispatch, or wiki queries.

Concise implementation plan for an accepted task before edits: dependencies, stops, verification checkpoints. Not for raw requirements, slicing, implementation, readiness, dispatch, or wiki.

Throwaway logic/state/UI/static-HTML prototype for a specific interaction, visual, or business-rule question. Not production code, backend/API truth, readiness, durable docs, or handoff.

Explicit project-level LLM Wiki create, ingest, query, audit, update, deprecate/archive, or repair. Not for direct answers, PRD shaping, slicing, implementation, verification, handoff, dispatch, or scratch notes.