AFK Artifact Workflow

This skill owns artifact boundaries, storage, and next-artifact suggestions. It does not choose the full skill sequence; return to afk-compass when the next phase needs planning, elicitation, trade-offs, execution discipline, debugging, review, UI, or documentation polish.

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

Artifact Boundaries

• PRD explains product intent: user problem, goals, scope, non-goals, success criteria, and stakeholder context.
• Spec explains behavior and design decisions: user flow, expected behavior, acceptance criteria, edge cases, constraints, and relevant design references. In small or solo contexts, PRD and spec can be combined when one artifact covers both responsibilities.
• If the PRD or combined artifact lacks behavior needed for implementation, create or update a spec before writing the implementation plan.
• RFC explains a proposed direction and invites review and feedback before implementation planning.
• Implementation Plan is the technical execution artifact: files, types, interfaces, pseudocode, tasks, and build strategy.
• Tracking follows the implementation plan and records execution status, checkpoints, validation, and handoff notes.

Artifact Storage