aidlc-verify

Score documentation readiness for AI execution and Jira transfer.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill aidlc-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-verify
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/aidlc/skills/aidlc-verify
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill aidlc-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that all essential project documentation (Intent, Units, Tasks, and Design) is complete and provides sufficient context for AI tooling to execute reliably and for Jira transfers to proceed with confidence. It coordinates parallel sub-agents to review content, refine Bolt groupings, and gate transfers based on defined confidence thresholds.

Core Features & Use Cases

  • Parallel verification: Launches per-Unit sub-agents to evaluate documentation quality and readiness.
  • Consolidated assessment: Aggregates results, surfaces gaps, strengths, and cross-unit implications to inform decisions.
  • Jira transfer gating: Transfers to Jira only when confidence criteria are met, with traceable artifacts and rollback options.
  • Bolt execution planning: Produces a Bolt Execution Plan that maps tasks to phases, lanes, and dependencies.

Quick Start

Start a verification run on the current project documentation to assess readiness for Jira transfer.

Frequently Asked Questions about aidlc-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify documentation readiness for AI-driven execution?

To check Jira transfer readiness, run a verification assessment that gates transfers based on defined confidence thresholds. The system aggregates documentation scores and only permits the Jira transfer when confidence criteria are met, providing traceable artifacts and rollback options.

How does parallel verification work for project documentation?

Documentation gating for Jira transfer works by setting defined confidence thresholds that must be met before any transfer proceeds. The system evaluates readiness across Units, Tasks, and Design docs, only allowing transfers with traceable artifacts and rollback options when criteria are satisfied.

What is a Bolt Execution Plan and how is it produced?

Consolidated assessment results include confidence scores, identified documentation gaps, recommended actions, and Jira transfer readiness. The system aggregates evaluations from parallel per-Unit sub-agents to inform your decisions on cross-unit implications and Bolt execution planning.

Do I need Confluence design docs to assess AI readiness?

Sub-agents refine Bolt groupings by reviewing your Units, Tasks, and Design documentation during the parallel verification run. They evaluate content quality and readiness, mapping tasks to execution phases, lanes, and dependencies to produce a comprehensive Bolt Execution Plan.