agentleFS
Sign inStart free
tuana-vntuana-vn/system-reverse-engineer/.github/skills/implementation-readiness-certification/SKILL.md

implementation-readiness-certification

Skill0 starsChanged 2 months agoMITView on GitHub

Certify whether a requirement-driven change is ready for implementation by verifying the complete traceability chain from requirement through gap analysis, TDD, design artifacts, verified detailed designs, WBS, and tests, with no unresolved source-resolvable high-impact gaps.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    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
  1. Distinctive:

    all detailed designs + verification reports

    line 32
  2. Distinctive:

    No material requirement/gap may be orphaned.

    line 44
  3. Distinctive:

    no high-impact claim relies only on stale generated prose

    line 51
  4. Distinctive:

    no unresolved provenance/exposure gap affects implementation

    line 52
  5. Distinctive:

    no source-resolvable HIGH/CRITICAL open question remains

    line 53
  6. Distinctive:

    all implementation-relevant artifacts registered

    line 61
  7. Very specific:

    all required artifacts DD_VERIFIED

    line 62
  8. Distinctive:

    Use the active workflow-declared implementation-readiness output path.

    line 103
  9. Very specific:

    Before IMPLEMENTATION_READY, verify the WBS contains no effort/duration estimates unless an explicit separate effort-estimation artifact is …

    line 108
  10. Distinctive:

    If unauthorized effort estimates are present:

    line 111

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Implementation Readiness Certification

Purpose

Implementation readiness is not "the documents look complete".

Certify the full chain:

REQ
→ GAP
→ TDD
→ DESIGN ARTIFACT
→ VERIFIED DD
→ VERIFIED WBS
→ TEST / VERIFICATION

Inputs

  • requirement
  • current-state analysis
  • gap/compliance analysis
  • TDD + verification
  • artifact registry
  • all detailed designs + verification reports
  • WBS + verification
  • contract/regression test design
  • open-question/evidence state

1. Traceability Closure

Required matrix:

Requirement IDGap IDTDD DecisionArtifact IDDDWBS IDsTest IDsStatus

No material requirement/gap may be orphaned.

2. Evidence Health

Check:

  • current-source anchors still exist
  • no high-impact claim relies only on stale generated prose
  • no unresolved provenance/exposure gap affects implementation
  • no source-resolvable HIGH/CRITICAL open question remains
  • external blockers are named precisely

3. Design Health

Check:

  • TDD verified
  • all implementation-relevant artifacts registered
  • all required artifacts DD_VERIFIED
  • proposed-vs-existing boundaries clear
  • compatibility/non-goals preserved

4. Plan Health

Check:

  • WBS_VERIFIED
  • dependencies implementable
  • missing-work search completed
  • tests/verification mapped
  • done criteria concrete

5. Certification

Use exactly one:

  • IMPLEMENTATION_READY
  • IMPLEMENTATION_READY_WITH_EXTERNAL_BLOCKERS
  • NOT_READY_DESIGN_GAPS
  • NOT_READY_WBS_GAPS
  • NOT_READY_SOURCE_GAPS

Rules:

IMPLEMENTATION_READY requires:

unresolved source-resolvable CRITICAL = 0
unresolved source-resolvable HIGH = 0
unverified required DD artifacts = 0
HIGH/CRITICAL WBS findings = 0
material requirement traceability gaps = 0

External blockers may remain only when current repository/source cannot resolve them and the exact external evidence/dependency is named.

Output

Use the active workflow-declared implementation-readiness output path. Do not reuse legacy readiness artifacts.

4.0 WBS Purity Check

Before IMPLEMENTATION_READY, verify the WBS contains no effort/duration estimates unless an explicit separate effort-estimation artifact is an approved input.

If unauthorized effort estimates are present:

NOT_READY_WBS_GAPS

Reason: WBS_CONTAINS_UNAPPROVED_EFFORT_ESTIMATE

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free