Menu
Use ad-hoc to classify the current slice or task into type and readiness state using the tff state model.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when reviewing architecture decisions. C4 model, dependency inversion, hexagonal boundaries.
Use during discuss-slice and plan-slice to stress-test a spec or plan against domain vocabulary before approval.
Use during research-slice to build disposable experiments that answer technical uncertainty.
Use during project:init to scaffold repo-level agent configuration (CLAUDE.md, AGENTS.md, tracker labels).
Use when debugging. 4-phase investigation, root cause, minimal fix.
Use when implementing features/fixes. Iron law: ¬∃ production code without failing test.
| name | triage |
| description | Use ad-hoc to classify the current slice or task into type and readiness state using the tff state model. |
| version | 1.0.0 |
| tags | ["process","state-management"] |
Ad-hoc manual invocation when you need to classify a slice or task before deciding the next action. Maps the current item to tff's state model for consistent tracking.
| Type | Signal |
|---|---|
defect | Existing behavior is incorrect, broken, or violates an invariant |
improvement | New capability, optimization, or refactor that does not fix a defect |
| State | Condition | Next Action |
|---|---|---|
needs-triage | Type and scope are unclear | Gather context, classify type, estimate size |
needs-info | Missing requirements, reproduction steps, or domain context | Request specific information from user |
ready-for-agent | Requirements clear, no blockers | Proceed to discuss-slice or plan-slice |
ready-for-human | Requires user decision or sign-off before proceeding | Present options and wait for response |
wontfix | Out of scope, infeasible, or superseded | Document reason and close |
Read the current slice or task description. Check tff-tools state:diff for related items.
Apply the heuristics above. Present:
defect or improvement)If the user disagrees, adjust the classification. If the state is needs-info, list concrete, actionable follow-up questions.
Update the item's tracking metadata via tff-tools or equivalent. Items in needs-info return to needs-triage once new information arrives.
ready-for-agent skips questioning but should confirm an agent brief exists