skills.rest
cooperacode
cooperacodeOFFICIAL
Explore all skills by this author →
GitHub

requirements

Extract and structure sourced requirements from wiki pages for work items.

5|1|Updated May 3, 2026
Search Tags:#requirements#validation#wiki#artifact#acceptance-criteria#upstream
One-click install
npx skills add https://github.com/cooperacode/forge --skill requirements-cooperacode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/cooperacode/forge/tree/main/.forge/skills/requirements
Command: npx skills add https://github.com/cooperacode/forge --skill requirements-cooperacode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires validate_common.sh, and includes scripts (resource) components.

What problem does it solve?

This skill automatically extracts and structures all requirements from the active wiki, ensuring they are backed by sources and preventing invention of new requirements.

Core Features & Use Cases

  • Contextual extraction of functional requirements and acceptance criteria from Product items, and quality attributes plus constraints from Strategic items.
  • Source-backed documentation: preserves a citation to the wiki page or upstream artifact for every requirement.
  • Scope alignment: respects existing upstream frames (grandparent Strategic items and parent Product artifacts) to avoid scope drift.

Quick Start

Invoke the skill to generate a requirements artifact from the active wiki for the current work item.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I extract functional requirements and acceptance criteria from a wiki?▼

Extracting functional requirements and acceptance criteria from a wiki involves identifying product items and structuring them with source citations. This skill automates that extraction directly from the active wiki page.

What is the best way to structure strategic quality attributes and constraints from wiki content?▼

Structuring strategic quality attributes and constraints from wiki content requires identifying upstream artifacts and framing them properly. This skill extracts strategic items while respecting existing upstream scope to prevent drift.

Can I generate requirements artifacts without inventing unsupported content?▼

Generating requirements artifacts without inventing unsupported content is possible by enforcing strict source backing. This skill ensures every structured requirement is cited to a wiki page or upstream artifact, eliminating fabricated specifications.

How do I align extracted requirements with upstream parent product artifacts?▼

Aligning extracted requirements with upstream parent product artifacts requires validating against grandparent strategic items. This skill uses upstream context to maintain scope alignment and prevent drift when structuring your requirements.

Does wiki requirement extraction work for both strategic and product work items?▼

Wiki requirement extraction works for both strategic and product work items by applying contextual rules. It identifies quality attributes and constraints for strategic items, and functional requirements with acceptance criteria for product items.

Related Skills

Explore More Product & Management Skills→
cooperacodecooperacode
5

der

Extract entities and relationships from wiki pages into a Mermaid ER diagram.

Official
Advanced
ZxelaZxela

review

Validate software changes against acceptance criteria and design artifacts.

Community
Intermediate
mrilikecodingmrilikecoding

citation-audit

Audit paper citations for existence, claim alignment, and bias patterns.

Community
Advanced
jabrenajabrena
423

032-architecture-adr-non-functional-requirements

Create Architectural Decision Records for non-functional requirements using the ISO/IEC 25010:2023 quality model.

Community
Advanced