Requirements
- 2.7k repo stars
- Updated May 4, 2026
- stellarlinkco/myclaude
Drive requirements-first feature development with quality gates so scope and acceptance are pinned before implementation.
About
This skill enforces a requirements-driven development workflow with quality gates, so a feature's requirements and acceptance criteria are pinned down before implementation begins. Developers use it when they want disciplined scoping and checkpoints rather than jumping straight into code, reducing rework from vague specs.
- Requirements-driven workflow
- Quality gates
- Practical feature implementation focus
Requirements by the numbers
- Data as of Aug 5, 2026 (Skillselion catalog sync)
/plugin marketplace add stellarlinkco/myclaude/plugin install requirements@myclaudeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2.7k |
|---|---|
| Last updated | May 4, 2026 |
| Repository | stellarlinkco/myclaude ↗ |
What it does
Drive requirements-first feature development with quality gates so scope and acceptance are pinned before implementation.
README.md
requirements - Requirements-Driven Workflow
Lightweight requirements-to-code pipeline with interactive quality gates.
Installation
python install.py --module requirements
Usage
/requirements-pilot <FEATURE_DESCRIPTION> [OPTIONS]
Options
| Option | Description |
|---|---|
--skip-tests |
Skip testing phase entirely |
--skip-scan |
Skip initial repository scanning |
Workflow Phases
| Phase | Description | Output |
|---|---|---|
| 0 | Repository scanning | 00-repository-context.md |
| 1 | Requirements confirmation | requirements-confirm.md (90+ score required) |
| 2 | Implementation | Code + requirements-spec.md |
Quality Scoring (100-point system)
| Category | Points | Focus |
|---|---|---|
| Functional Clarity | 30 | Input/output specs, success criteria |
| Technical Specificity | 25 | Integration points, constraints |
| Implementation Completeness | 25 | Edge cases, error handling |
| Business Context | 20 | User value, priority |
Sub-Agents
| Agent | Role |
|---|---|
requirements-generate |
Create technical specifications |
requirements-code |
Implement functionality |
requirements-review |
Code quality evaluation |
requirements-testing |
Test case creation |
Approval Gate
One mandatory stop point after Phase 1:
- Requirements must achieve 90+ quality score
- User must explicitly approve before implementation begins
Testing Decision
After code review passes (≥90%):
--skip-tests: Complete without testing- No option: Interactive prompt with smart recommendations based on task complexity
Output Structure
.claude/specs/{feature_name}/
├── 00-repository-context.md
├── requirements-confirm.md
└── requirements-spec.md
When to Use
- Quick prototypes
- Well-defined features
- Smaller scope tasks
- When full BMAD workflow is overkill
Directory Structure
agents/requirements/
├── README.md
├── commands/
│ └── requirements-pilot.md
└── agents/
├── requirements-generate.md
├── requirements-code.md
├── requirements-review.md
└── requirements-testing.md
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k