Requirements
Turn vague product ideas into a structured requirements document through guided multi-phase questioning before you commit engineering time.
Overview
requirements is a plugin marketplace for the Validate phase that produces structured requirements documents via iterative Claude dialogue.
What is this marketplace?
- Iterative dialogue across phases to clarify fuzzy ideas
- Outputs a requirements document with lifecycle management
- Bilingual-friendly tags (要件定義, 基本設計, 仕様書) for JP/EN product work
- Single requirements plugin at marketplace version 1.1.0
- Marketplace bundles 1 plugin (requirements v1.1.0)
What problem does it solve?
Jumping straight into code when the idea is still fuzzy leads to rework, scope creep, and missing acceptance criteria.
Who is it for?
Solo founders scoping an MVP, feature, or client project who want PM-style rigor without a separate spec tool.
Skip if: Teams that already maintain formal PRDs in Notion/Jira with locked sign-off and no need for agent-led discovery.
What do I get? / Deliverables
After registration, you get a clarified, lifecycle-managed requirements document you can use to prototype, estimate, and build with alignment.
- Structured requirements document from the requirements plugin
- Lifecycle-managed spec revisions as scope changes
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
How it compares
Requirements-definition plugin marketplace, not an MCP server or codegen skill.
Common Questions / FAQ
Who is Requirements for?
Builders and product-minded solos who need 要件定義-style clarity and a written spec before writing code.
When should I use Requirements?
Use it at the start of a new product, major feature, or client engagement when goals and constraints are still implicit.
How do I add Requirements to my agent?
Add the 555takakusaki/Requirements-plugin marketplace in Claude Code and enable the Requirements plugin from the published manifest (v1.1.0).