qfai-require

Register input sources and generate a minimal requirement index for SDD preflight.

3|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/aganesy/QFAI --skill qfai-require
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qfai-require
Source: https://github.com/aganesy/QFAI/tree/main/packages/qfai/assets/init/.qfai/assistant/skills/qfai-require
Command: npx skills add https://github.com/aganesy/QFAI --skill qfai-require

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of capturing and organizing source traceability and creating a minimal requirement index for preflight checks before more detailed specification work begins.

Core Features & Use Cases

  • Source Registration: Indexes and registers all input sources (files, URLs, text) with stable identifiers.
  • Requirement Indexing: Extracts minimal requirement statements, linking them directly to their sources.
  • Open Question Logging: Identifies and logs missing information or ambiguities.
  • Use Case: Before drafting detailed software specifications, use this Skill to quickly catalog all relevant design documents, user feedback, and existing code snippets, ensuring that the subsequent specification process is grounded in traceable evidence.

Quick Start

Use the qfai-require skill to collect source inputs and create a minimal requirement index.

Frequently Asked Questions about qfai-require

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

FAQPage Schema
How do I index requirements and evidence for software specification preflight?

To index requirements and evidence, you capture source traceability and generate a minimal requirement index, ensuring all inputs are registered and linked to extracted requirement statements for preflight checks.

What is the best way to link source traceability to extracted requirement statements?

The best way to link source traceability is by registering all input sources with stable identifiers and connecting them directly to the minimal requirement statements extracted during the indexing process.

How do I log open questions and missing information during requirements indexing?

You log open questions and missing information during requirements indexing by identifying ambiguities within the collected sources and recording them alongside the generated minimal requirement index for subsequent review.

Can I use indexed requirements to catalog design documents and user feedback before drafting specifications?

Yes, you can use indexed requirements to catalog design documents, user feedback, and existing code snippets, ensuring the subsequent specification process is grounded in traceable evidence.

Does requirements indexing support strict output path and file naming conventions?

Yes, requirements indexing supports strict output path and file naming conventions by managing open questions and producing evidence for review while adhering to these specified output constraints.