| name | agentic-requirement-clarity |
| description | Use for deterministic P0A1 requirement clarity lint/doctor/repair/confirm, P0A2 assess, and P0B route-pre-spec/create-batch/apply-response operations. |
| argument-hint | lint|doctor|repair|confirm --manifest <path> | assess --source-set <path> --ledger <path> --phase-id <id> --output-dir <path> | route-pre-spec --input <path> | create-batch --manifest <path> --round <1|2> | apply-response --batch <path> --responses <path> |
Agentic Requirement Clarity
This skill owns the deterministic P0A1 requirement clarity artifacts:
requirement-source-setrequirement-clarity-ledgerrequirement-clarity-gate
Stable command:
agentic requirement-clarity lint --manifest docs/assets/builder/requirement-clarity/<phase-id>.manifest.yaml <workspace>
Module fallback:
PYTHONPATH=python python -m agentic_core.cli requirement-clarity lint --manifest docs/assets/builder/requirement-clarity/<phase-id>.manifest.yaml <workspace>
P0A1 does not ask user clarification questions, run real extraction, interpret images, generate prototypes, or activate agentic-coding-spec pre-spec routing.
P0A2 Extraction Integration
P0A2 enables non-fixture agentic requirement-clarity assess --source-set ... --ledger ... --phase-id ... --output-dir ... <workspace>.
It produces fact packet files, updates the requirement clarity ledger and manifest diagnostics, then immediately runs P0A1 lint.
P0A2 still does not ask user clarification questions, activate agentic-coding-spec pre-spec routing, or write assumptions into final Superpowers specs. Those remain P0B.
See rules/extraction.md.
P0B Clarification Routing
P0B enables parser-backed clarification routing:
agentic requirement-clarity route-pre-spec --input <route-input.yaml> <workspace>
agentic requirement-clarity create-batch --manifest <manifest> --round <1|2> <workspace>
agentic requirement-clarity apply-response --batch <batch> --responses <responses.yaml> <workspace>
agentic-coding-spec is the only Phase 6.5 trigger caller. Requirement clarity consumes the validated decision object and must not parse Phase 6.5 requests itself.
After a validated Phase 6.5 non-trigger, P0B HITL routing is active for unresolved business blockers in scope, roles/responsibility, permissions, processes, states, and acceptance. UI/design preferences do not block here; leave them for brainstorming/prototype flows.
See rules/clarification.md.
