doc-req-autopilot_skill

Overview

This skill automates creation of atomic REQ documents from SYS specifications and scores them for SPEC-Ready and IMPL-Ready readiness. It decomposes monolithic SYS requirements into multiple self-contained REQ files (one per capability) following REQ v3.0 12-section structure and cumulative traceability. The pipeline performs pre-generation SYS validation, real-time quality feedback during generation, and iterative validation and fixes until target readiness scores are met.

How this skill works

The autopilot detects input type (SYS or REQ) and either generates atomic REQ files from SYS modules or runs review workflows on existing REQ directories. It validates SYS readiness (REQ-Ready >= 90%), decomposes functional requirements into 10–15 capability files per module, fills all 12 REQ sections, and computes SPEC-Ready and IMPL-Ready scores. The orchestration delegates structure rules, validation, review, quality advice, naming, and fixes to specialized skills and iterates auto-fixes until thresholds pass or manual review is required.

When to use it

• You have completed SYS documents and want automated REQ decomposition into atomic capability files.
• You need REQ v3.0 outputs with 12 required sections and cumulative traceability tags.
• You want automated SPEC-Ready and IMPL-Ready scoring and auto-fix cycles before review.
• You must generate an indexed folder of self-contained REQ files for a module.
• You need cross-linked capabilities with discoverability tags for downstream SPEC generation.

Best practices

• Ensure SYS documents meet REQ-Ready thresholds (recommended >= 90%) before running generation.
• Use the monolithic mode only when modules have ≤2 functional requirements or explicit manual needs.
• Provide clear priority and verification expectations in SYS to improve scoring and reduce iterations.
• Keep atomic files under configured size limits; split large requirements to preserve single-responsibility.
• Review the generated index file to validate cross-reference matrices and discovered dependencies.

Example use cases

• Generate REQ-01 module: decompose SYS-01 into an index and 10–15 capability REQ files with SPEC-Ready scores.
• Review existing REQ directory: run review workflow to compute quality scores and produce fix recommendations.
• Batch generation: process multiple SYS inputs (SYS-01,SYS-02) and create separate REQ folders per module.
• Auto-fix cycle: detect missing performance/security attributes in SYS, apply templates, and revalidate.
• Prepare downstream SPEC: produce SPEC-ready atomic REQs ready for automated SPEC artifact generation.