check-readiness
Skill2 starsChanged 2 months agoMITView on GitHub
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'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- rterakedis/leanwheel-skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rterakedis/leanwheel-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- agents-mdSkill
- agent-workflow-engineeringSkill
- analyze-architectureSkill
- architecture-auditSkill
- ask-mattSkill
- ci-cd-and-automationSkill
- codebase-contextSkill
- decision-memorySkill
- delegation-protocolSkill
- dependency-analysisSkill
- diagnosing-bugsSkill
- dispatching-parallel-agentsSkill
- documentation-maintenanceSkill
- engineering-closeoutSkill
- environment-discoverySkill
- github-pr-workflowSkill
- implementSkill
- interview-meSkill
- parallel-feature-developmentSkill
- planning-and-task-breakdownSkill
- project-contextSkill
- project-retrospectiveSkill
- release-managementSkill
- requesting-code-reviewSkill
- solution-architectureSkill
- subagent-driven-developmentSkill
- synthesize-project-contextSkill
- task-intakeSkill
- workflow-definitionSkill
- workflow-runnerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ask: Which phase are you about to start?
- Very specific: line 30
Read _superml/config.yml and check the artifacts section.
- Very specific: line 52
If a flag is true but the file is missing: flag as INCOMPLETE (config/file mismatch).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdIf 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)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.