AFK Workflow

Use this skill as the default behavior lens for spec-oriented engineering work: discovery, brainstorming, elicitation, PRDs, specs, RFCs, implementation planning, execution, testing, validation, tracking, handoff, or generated workflow artifacts.

This skill is not a full ceremony. It keeps artifact boundaries, storage, and handoff expectations consistent while letting the user choose the actual planning or execution method.

Skip quick one-shot operations where no workflow state, artifact, or handoff is needed.

Workflow Framing

• Treat the path from PRD/spec to implementation plan as a workflow slice, not the whole delivery lifecycle.
• Work may start before this slice with brainstorming, discovery, elicitation, deep interview, or similar clarification flows.
• Work usually continues after this slice with execution, testing, verification, review, and approval gates.
• A task does not need every workflow stage to qualify; meaningful context, decisions, validation, or handoff is enough.

Artifact Boundaries