web-requirements

Generates web project user stories with Gherkin acceptance criteria from Swarm-driven analysis and story mapping.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/sizukutamago/dev-tools-plugin --skill web-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-requirements
Source: https://github.com/sizukutamago/dev-tools-plugin/tree/main/skills/web-requirements
Command: npx skills add https://github.com/sizukutamago/dev-tools-plugin --skill web-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Web teams often struggle to capture complete requirements and convert them into testable user stories. This Skill uses Swarm-powered analysis to surface gaps, align stakeholders, and deliver a ready-to-use requirements document.

Core Features & Use Cases

  • Swarm-powered discovery across tech, domain, UI, integration, and non-functional requirements to surface diverse perspectives.
  • User story generation with Gherkin acceptance criteria (As a / I want to / So that with Given/When/Then).
  • End-to-end traceability outputs (story maps, open questions, and unified context) for collaboration and review.

Quick Start

Provide a feature prompt such as: "Define the requirements for a checkout flow." The workflow will perform scope estimation, explorer swarm analysis, interviewer questions, planner structuring, writer output, and reviewer checks to produce a finalized user-stories.md.

Frequently Asked Questions about web-requirements

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

FAQPage Schema
How do I generate user stories with Gherkin acceptance criteria from a feature prompt?

You can generate user stories with Gherkin acceptance criteria by providing a feature prompt like a checkout flow description. The system performs swarm analysis and structures outputs into Epics, Features, and Stories with Given/When/Then formats.

What is the best way to structure requirements for a brownfield web project?

To structure requirements for a brownfield web project, this approach uses swarm-driven analysis to evaluate existing contexts. It surfaces integration and non-functional gaps, aligning stakeholders before mapping out MVP scope and testable user stories.

Can I use swarm analysis to discover missing non-functional requirements?

Yes, swarm-powered discovery analyzes tech, domain, UI, integration, and non-functional requirements. This multi-perspective analysis surfaces diverse perspectives and hidden gaps to align stakeholders before finalizing the user stories document.

Do I need Python3 to create story maps and traceability outputs?

Yes, Python3 is a required dependency to run the scripts that execute the swarm-driven workflow. It processes the scope estimation, explorer analysis, and planner structuring to output story maps and traceability documents.

Why use Gherkin acceptance criteria for web project requirements?

Gherkin acceptance criteria enforce a strict Given/When/Then structure that ensures testable outcomes. By defining stories as As a/I want to/So that, it bridges the gap between initial ideas and implementation readiness for web teams.