requirement-architect
Rewrites software requirements to lead to better code design and architecture. Use this skill whenever a user shares requirements, user stories, feature specs, acceptance criteria, or PRDs and wants them improved before development begins. Also trigger when a user says 'review my requirements', 'improve this spec', 'make this requirement better', 'rewrite this for better design', 'architecture-aware requirements', or asks how to write requirements that produce cleaner code. Trigger even when users paste requirements without explicitly asking for review — if the requirements contain design-limiting patterns (conditional chains, implementation details, ambiguous boundaries), proactively suggest improvements.
Install
With your agent
Install OMGSkills skill "incubyte/ai-plugins:bee/skills/requirement-architect" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/incubyte/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/bee/skills/requirement-architect ~/.claude/skills/requirement-architect
From README
Requirement Architect A skill that rewrites software requirements so they naturally lead to better software design, architecture, and code quality. Why This Matters Research by Perry & Wolf (1992) established that software architecture = elements + form + rationale, and that requirements directly constrain architectural choices. Boehm's empirical work showed that requirements errors cost 50-200x more to fix when caught late. But there's a subtler problem: even "correct" requirements can lead to poor architecture if they're written in ways that embed implementation assumptions. The key insight: how you describe behavior in a requirement shapes how a developer implements it in code. A requirement full of if/else conditional logic produces code full of if/else branches. A requirement that describes distinct types and their behaviors produces polymorphic, extensible code. The requirement is a mold — the code takes its shape.
More from this repo
ai-ergonomics
This skill should be used when evaluating how well code supports LLM-assisted development.
ai-workflow
This skill should be used when explaining why Bee follows spec-first TDD workflows, or when teaching mode is on.
architecture-patterns
This skill should be used when evaluating architecture options, checking dependency direction, or deciding between...
