Kicchann Reqord
kicchann-reqord is a Claude Code plugin for the Validate phase that keeps structured YAML and Markdown requirements in git next to your codebase for AI-assisted delivery.
by kicchann · github.com/kicchann/reqord
Install when you want git-native requirements—structured YAML and Markdown beside your code—so Claude can scope and implement against versioned specs.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kicchann-reqord@kicchann/reqordBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:kicchann/reqord") and the paste-ready config with skillselion.get_install_config("plugin:kicchann/reqord").
What it does
kicchann-reqord is a Claude Code plugin for git-native requirements management: structured YAML and Markdown that live in the same repository as the product you are shipping with agents. Solo builders use it to stop losing scope in chat logs—each requirement becomes a file the agent can read, you can review in pull requests, and you can branch like any other source asset. Catalog metadata describes one plugin with keywords reqord and requirementspecification, placing it primarily in Validate scope while remaining useful in Build PM and Ship review when you verify implementation against written specs. It pairs naturally with planning skills: approved requirements should precede large codegen tasks. Complexity is beginner-friendly if you already use git; the discipline is keeping YAML schemas consistent. Skip it if you prefer heavyweight ALM outside the repo or only need informal todo lists without structured fields.
Highlights
- Git-native requirements management designed for the AI coding era
- Structured YAML plus Markdown artifacts version-controlled with application code
- Single-plugin Claude Code bundle focused on requirementspecification workflow
- Keeps specs diffable in PRs instead of orphaned Notion or chat promises
- Development-category plugin aligned with reqord keyword taxonomy
Why builders use it
Agent coding drifts when requirements live only in threads instead of versioned, reviewable spec files beside the code.
After install, you maintain diffable requirement specs in the repo that Claude can load before scoping and implementing features.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is kicchann-reqord for?
It is for developers using Claude Code who want requirements as YAML and Markdown in git rather than disposable chat instructions.
When should I use kicchann-reqord?
Use it when scoping a feature or epic, before large agent implementation passes, and when reviewing shipped work against written specs.
How do I add kicchann-reqord to my agent?
Install the kicchann/reqord Claude Code plugin, add reqord spec files to your repository layout, then point Claude at those paths in validate and build sessions.
Comments
Share how you use kicchann-reqord, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.