📝
WritingPython

Extracting Requirements

by prime-radiant-inc

Extracting Requirements is a Writing skill for Claude Code, published by prime-radiant-inc in iterative-development.

179 stars17 forkson prime-radiant-inc/iterative-developmentAdded 2026/09/07+1% in starsRepository updated 2026/06/06
ai-agentsautonomous-agentsclaude-codeclaude-code-pluginmethodology
Install in seconds
Install Extracting Requirements
Copy Extracting Requirements into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/prime-radiant-inc/iterative-development/tree/main/skills/extracting-requirements ~/.claude/skills/extracting-requirements

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/prime-radiant-inc/iterative-development.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/extracting-requirements/SKILL.md in prime-radiant-inc/iterative-development
Installs to
~/.claude/skills/extracting-requirements
Collection
One of 6 skills cataloged from this repository
Category
Writing1328 skills

What Extracting Requirements does

Extracting Requirements reads human spec collateral and turns it into per-epic requirement files with proof obligations plus reusable behavior scenarios with stable IDs. Use it when bootstrapping or regenerating requirements for an iterative-development run.

Extracting Requirements is cataloged under Writing on DirSkills. Extracting Requirements comes from a repository tagged ai-agents, autonomous-agents, claude-code, claude-code-plugin and methodology.

Documentation

README

Extracting Requirements

Overview

Reads arbitrary human spec collateral and produces two artifact sets:

  1. Per-epic requirement files in docs/superpowers/iterations/requirements/ — story cards with proof obligations per AC
  2. Behavior scenarios in docs/superpowers/iterations/behavior-scenarios.md — reusable observable-behavior contracts with stable IDs

Uses a chunking + parallel-dispatch + aggregation pipeline so that no single agent holds the entire spec in context. Handles specs from a single page up to ~100K tokens across dozens of files.

When to Use

Invoked by iterative-development during bootstrap, or standalone when you need to regenerate requirements from human spec collateral.

Script Location

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Extracting Requirements

  • What else does prime-radiant-inc publish alongside Extracting Requirements?

    Extracting Requirements is one of 6 skills that DirSkills catalogs from prime-radiant-inc/iterative-development, the repository it ships in. Its siblings there include Auditing Progress, Implementing Tasks and Iterative Development. Each one is a separate skill with its own page in this directory, installs the same way Extracting Requirements does, and is maintained by prime-radiant-inc in that same repository. The rest of the collection is listed on the prime-radiant-inc/iterative-development page.

  • How does Extracting Requirements compare to other Writing skills?

    Extracting Requirements ranks #1123 by stars among the 1328 Writing skills in this catalog. The most-starred ones next to it are Article Writing, Social Media Content Calendar and Knowledge Comic Creator. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Extracting Requirements against them. Open each page to compare what they document and how they install.

More from prime-radiant-inc/iterative-development

Extracting Requirements is one of 6 skills cataloged on DirSkills from prime-radiant-inc/iterative-development.

See all 6 skills
🔍
2h ago

Auditing Progress

Auditing Progress checks evidence quality after an iteration using three tiers: current stories, impacted scenarios, and sentinel regressions. Use it when you need to verify that behavior proof is durable before moving to the next iteration.
Quality
17917
🛠️
2h ago

Implementing Tasks

Implementing Tasks executes an in-memory batch of TDD-sized tasks through an implementer subagent, then spec-compliance and code-quality review loops. Use it during a running iteration when tasks need to be completed one by one with per-task status reported back.
AI Engineering
17917
🔁
2h ago

Iterative Development

Iterative Development turns a large or ambiguous spec into a walking skeleton, then runs audited sprints that build behavior evidence for each externally visible requirement. Use it when you need a working, testable product at every iteration boundary.
AI Engineering
17917
🔁
2h ago

Running An Iteration

Running An Iteration executes the next pending roadmap iteration by reviewing scope, baselining sentinel scenarios, dispatching implementation and evidence tasks, and updating iteration artifacts. Use it in an iterative-development loop when advancing one iteration at a time.
AI Engineering
17917
🧭
2h ago

Scoping The Simplest Core

Scoping The Simplest Core turns extracted requirements into a roadmap with a walking-skeleton iteration and follow-on iterations. It is used to choose the first runnable journey scenario, split stories by dependency profile, and validate scope via review.
AI Engineering
17917