requirements-stories
v1.0.0Conversational requirements-definition and user-story facilitator. Elicits requirements and grows an agile product backlog (personas, epics, user stories with acceptance criteria, EARS-worded NFRs, a story map, and prioritization) into one backlog.yaml source of truth, validated for INVEST/EARS/structure quality, then generate-forwards a Markdown backlog and Gherkin feature files. Traces every story back to an ArchiMate ea-model.yaml (read-only upstream) and checks bidirectional requirement coverage, bridging archimate-ea to archimate-to-impl. Works standalone without an EA model.
By dobachi0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Aug 30, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install requirements-stories@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/dobachi/claude-skills-marketplaceClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/requirements-stories/.
Plugin files
├── .claude-plugin/plugin.json└── skills/requirements-stories/SKILL.md
Included Skills1
Facilitate requirements definition and agile user-story work. Conversationally elicit requirements and grow a product backlog — personas, epics, user stories with acceptance criteria (Given-When-Then / rules), EARS-worded non-functional requirements, a story map, and prioritization (MoSCoW / WSJF) — into ONE backlog.yaml (the single source of truth), validated for INVEST/EARS/structure quality, then generate-forward a Markdown backlog and Gherkin feature files. Every story can trace back to an ArchiMate ea-model.yaml (read-only upstream) with a bidirectional coverage check, bridging archimate-ea to archimate-to-impl. Works standalone with no EA model. Use when the user wants to do 要求定義 / requirements definition, write or refine ユーザーストーリー / user stories, build a product backlog, split or prioritize stories, write acceptance criteria, or turn EA requirements into a dev backlog.
Plugin manifests1
{
"name": "requirements-stories",
"description": "Conversational requirements-definition and user-story facilitator. Elicits requirements and grows an agile product backlog (personas, epics, user stories with acceptance criteria, EARS-worded NFRs, a story map, and prioritization) into one backlog.yaml source of truth, validated for INVEST/EARS/structure quality, then generate-forwards a Markdown backlog and Gherkin feature files. Traces every story back to an ArchiMate ea-model.yaml (read-only upstream) and checks bidirectional requirement coverage, bridging archimate-ea to archimate-to-impl. Works standalone without an EA model.",
"version": "1.0.0",
"author": {
"name": "dobachi"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[requirements-stories on Agent Plugins Marketplace](https://pluginsmp.com/plugins/requirements-stories)