How do I install the Check Readiness skill?

Run npx skillmds@latest add gabrielmoreira/check-readiness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Check Readiness safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Check Readiness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Check Readiness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Check Readiness?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Check Readiness by gabrielmoreira — Agent Skill

Name: Check Readiness
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Check Readiness

Verify that all prerequisite artifacts exist and are complete before starting the next phase. Use when the user says 'are we ready to start development', 'check readiness', or 'verify phase prerequisites'.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Readiness Check Workflow

Goal

Confirm that every required artifact for the upcoming phase is present, complete, and signed off. Produce a clear go / not-ready decision with a specific remediation list for any gaps.

Step 1: Identify the Target Phase

Ask: Which phase are you about to start?

Planning (needs: PRD)
Architecture (needs: PRD, product sign-off)
Team Lead / Sprint Planning (needs: Architecture doc, Epics)
Development (needs: Sprint plan, Stories with ACs)
QA (needs: Development sign-off, all stories implemented)
Release (needs: QA sign-off, release checklist)

Step 2: Check Required Artifacts

For the chosen phase, verify each prerequisite:

Read _superml/config.yml and check the artifacts section.

Artifact	Config Key	Status
PRD	`prd_complete`	✔ / ✗
Architecture doc	`architecture_complete`	✔ / ✗
Epics & Stories	`epics_complete`	✔ / ✗
Dev sign-off	`implementation_signed_off`	✔ / ✗
QA sign-off	`qa_signed_off`	✔ / ✗

Step 3: Verify File Existence

For each artifact flagged true in config, verify the file actually exists:

{docsPath}/product/prd.md
{docsPath}/architecture/architecture.md
{docsPath}/planning/epics.md

If a flag is true but the file is missing: flag as INCOMPLETE (config/file mismatch).

Step 4: Readiness Decision

READY — all prerequisites are marked complete and files exist.

✅ All prerequisites confirmed. You're ready to start [phase name].

NOT READY — one or more prerequisites are missing or incomplete.

❌ Cannot start [phase name]. Missing prerequisites:

[artifact] — [action to fix]

[artifact] — [action to fix]

Step 5: Output

Log the readiness check to {docsPath}/planning/readiness-check-{date}.md with:

Phase being checked
Each artifact: status + file path
Go / Not-Ready decision
Remediation steps (if not ready)

---name: check-readinessdescription: Verify that all prerequisite artifacts exist and are complete before starting the next phase. Use when the user says 'are we ready to start development', 'check readiness', or 'verify phase prerequisites'.--- # Readiness Check Workflow ## Goal Confirm that every required artifact for the upcoming phase is present, complete, and signed off. Produce a clear go / not-ready decision with a specific remediation list for any gaps. --- ## Step 1: Identify the Target Phase Ask: Which phase are you about to start? - [ ] Planning (needs: PRD) - [ ] Architecture (needs: PRD, product sign-off) - [ ] Team Lead / Sprint Planning (needs: Architecture doc, Epics) - [ ] Development (needs: Sprint plan, Stories with ACs) - [ ] QA (needs: Development sign-off, all stories implemented) - [ ] Release (needs: QA sign-off, release checklist) --- ## Step 2: Check Required Artifacts For the chosen phase, verify each prerequisite: Read `_superml/config.yml` and check the `artifacts` section. | Artifact | Config Key | Status | |----------|------------|--------| | PRD | `prd_complete` | ✔ / ✗ | | Architecture doc | `architecture_complete` | ✔ / ✗ | | Epics & Stories | `epics_complete` | ✔ / ✗ | | Dev sign-off | `implementation_signed_off` | ✔ / ✗ | | QA sign-off | `qa_signed_off` | ✔ / ✗ | --- ## Step 3: Verify File Existence For each artifact flagged `true` in config, verify the file actually exists: ``` {docsPath}/product/prd.md {docsPath}/architecture/architecture.md {docsPath}/planning/epics.md ``` If a flag is `true` but the file is missing: flag as **INCOMPLETE** (config/file mismatch). --- ## Step 4: Readiness Decision **READY** — all prerequisites are marked complete and files exist. > ✅ All prerequisites confirmed. You're ready to start [phase name]. **NOT READY** — one or more prerequisites are missing or incomplete. > ❌ Cannot start [phase name]. Missing prerequisites: > > 1. [artifact] — [action to fix] > 2. [artifact] — [action to fix] --- ## Step 5: Output Log the readiness check to `{docsPath}/planning/readiness-check-{date}.md` with: - Phase being checked - Each artifact: status + file path - Go / Not-Ready decision - Remediation steps (if not ready)

Frequently asked questions