Extracts requirements and generates a plan with traceability checkpoints.
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill planning-laf-us
Please help me install this Agent Skill. Skill: planning Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.ghcp-appmod/skills/planning Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill planning-laf-us
Planning a complex feature from a spec is error-prone and slow; this Skill automates the creation of an end-to-end implementation plan with traceability checkpoints, consolidating requirements, artifacts, and governance into a single workflow.
Provide a feature specification and run the planning workflow to produce a complete implementation plan with traceability checkpoints.
High-intent search queries and answers about installing and using this skill.
To turn feature specs into an actionable plan, provide the specification document to the planning workflow. It automatically extracts all REQ-XXX requirements, generates research notes, data models, and API contracts, and maps them to a sequential plan.
Requirement traceability works by mapping each generated artifact, including data models and API contracts, directly to extracted REQ-XXX identifiers. This process validates full coverage and generates a checkpoints file to report any gaps or deviations for remediation.
When planning a complex feature, the workflow automatically generates sequential artifacts including research notes, a data model, API contracts, and a comprehensive implementation plan with explicit mappings to the extracted requirements inventory.
Yes, you can validate requirements coverage before deployment. The workflow checks the assembled requirements inventory against generated artifacts, automatically creating a checkpoints file that highlights any coverage gaps or deviations requiring remediation.
The best way to automate API contract generation is to run a phase-driven planning workflow on your feature specification. It extracts requirements to build an inventory and sequentially generates research notes, data models, and the API contracts with traceability.
No, you do not need to manually extract REQ-XXX identifiers. The planning workflow automatically identifies all REQ-XXX requirements from the provided feature specification and assembles them into a requirements inventory for artifact generation.
microsoftCatalog codebase features into structured specs with REQ-XXX IDs.
reqvire-orgOrchestrate Reqvire commands for MBSE and requirements traceability workflows.
lexijamesesqDetect structural and voice deviations in strategy artifacts against format specs.
rezosndGenerate styled Excel workbooks with formulas, charts, and data validation.
