req-implement-test

Name: req-implement-test
Availability: InStock
Author: scarletfish

Standardize requirements elicitation with structured tables and user confirmation before implementation.

Updated Jun 8, 2026

Search Tags:#workflow #development #quality assurance #specification #requirements

Ready to run

npx skills add https://github.com/ScarletFish/MyAnimeDock --skill req-implement-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: req-implement-test
Source: https://github.com/ScarletFish/MyAnimeDock/tree/main/.agents/skills/req-implement-test
Command: npx skills add https://github.com/ScarletFish/MyAnimeDock --skill req-implement-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents development rework and scope creep by enforcing a mandatory, structured requirements elicitation process before any code is written.

Core Features & Use Cases

Structured Requirement Tables: Forces the definition of data sources, edge cases, and acceptance criteria.
Hard Gatekeeping: Prevents implementation until requirements are explicitly confirmed by the user.
Use Case: When a user requests a new feature, this skill guides the AI to research existing code, draft a comprehensive requirement table, and obtain formal user sign-off before starting development.

Quick Start

Use the req-implement-test skill to initiate a formal requirements gathering process for the proposed feature.

Frequently Asked Questions about req-implement-test

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

FAQPage Schema

How do I prevent scope creep and rework during software development?▼

A structured requirements elicitation workflow prevents scope creep by enforcing the creation of a comprehensive requirement table and explicit user confirmation before any code is written. This approach ensures alignment between user intent and technical implementation.

What is a structured requirement table for feature requests?▼

A structured requirement table is a formal specification document that forces the definition of data sources, edge cases, and acceptance criteria for feature requests, architectural changes, and UI modifications. It acts as a hard gatekeeper before implementation begins.

How to require user sign-off before starting technical implementation?▼

To require user sign-off, apply a hard gatekeeping process that guides the AI to research existing code, draft a comprehensive specification, and obtain formal user confirmation before proceeding to the implementation phase. This prevents unauthorized feature development.

Does this requirements gathering process work for UI modifications?▼

Yes, this requirements elicitation workflow explicitly applies to UI modifications, feature requests, and architectural changes. It standardizes the specification process to ensure technical implementation aligns with user intent across all software development tasks.

When do I need a formal requirements elicitation workflow?▼

You need a formal requirements elicitation workflow whenever a user requests a new feature, architectural change, or UI modification. It prevents development rework by enforcing specification drafting and user approval before coding starts.