Overview

The Check Implementation Readiness workflow verifies that PRD, UX, architecture, and epics specs are complete before implementation. It is driven by the Architect (Winston) in the CORE module and relies on instructions.md for execution and checklist.md for validation.

How This Skill Works

The skill guides the Architect (Winston) to read ./instructions.md, perform readiness checks across PRD, UX, Architecture, and Epics, and then validate the results against ./checklist.md before proceeding.

When to Use It

• When the user asks to 'check implementation readiness'.
• Before starting a new feature sprint that requires complete PRD/UX/Architecture/Epics.
• During a design review to confirm specs are fully defined.
• When epics need alignment with architecture and UX goals.
• After stakeholder inputs to ensure all docs are up to date.

Quick Start

1. Step 1: Prompt the skill with 'check implementation readiness' to trigger the workflow.
2. Step 2: The Architect (Winston) reads ./instructions.md and executes the prescribed steps.
3. Step 3: Compare results with ./checklist.md and confirm readiness to proceed.

Best Practices

• Always reference ./instructions.md for execution steps.
• Verify PRD completeness and traceability to Epics.
• Cross-check UX flows and user journeys against requirements.
• Confirm architecture diagrams and tech decisions are documented.
• Validate coverage against ./checklist.md before sign-off.

Example Use Cases

• Sprint kickoff: validate readiness before development starts.
• PM updates PRD: re-check readiness against checklist.
• Architect review: confirm all Epics are scoped and described.
• UX refresh: ensure UX specs align with PRD.
• Stakeholder consensus: finalize readiness check before release plan.

Frequently Asked Questions