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'.
- License 许可
- MIT
- 最近更新
- 2026-05-12
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- check-readiness
- description
- 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'.
03 SKILL.md 正文
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)
04 同仓库更多 Skills
jira-sync
Bulk sync all epics and stories from the local backlog to JIRA. Use when the user says 'sync to JIRA', 'push everything to JIRA', or 'create all JIRA tickets'.
jira-create-story
Create a single story ticket in JIRA from a local story file. Use when the user says 'create this story in JIRA' or 'push story to JIRA'.
jira-create-epic
Create an epic in JIRA from a planning artifact. Use when the user says 'create this epic in JIRA' or 'push epic to JIRA'.
jira-connect
Set up and verify JIRA integration. Use when the user says 'connect to JIRA', 'set up JIRA', or 'configure JIRA'.
jira-conflict-detect
Check if a story is already being worked on by another team member. Use before starting any story implementation.
gitlab-create-mr
Create a GitLab Merge Request for the current story branch. Use when the user says 'create an MR', 'open a merge request', or 'ready for review' in a GitLab project.