Requirement clarity is handled by this skill in a buyer-readable, reusable workflow.
Traceability is handled by this skill in a buyer-readable, reusable workflow.
SB_srs_governor@SB_srs_governorAgent SetupLevel 2 Guided Skill15 minutes
What is this?
A paid requirements-governance skill that reviews and controls a Software Requirements Specification (SRS) before it becomes the build contract. Turn a useful SRS draft into a governed requirement source with clearer scope, traceability, and change control. Use it when you need help with Use it when you already have a product brief or SRS draft, but are not sure it is clear enough to become the build contract and Use it when requirements still contain contradictions, missing acceptance criteria, unclear ownership, or casual edits. Without it, teams usually keep suffering through Stronger requirement source and Less scope drift. The buyer can use it to produce SRS review and Change-control notes with a clearer next step and less prompt guesswork. It is especially useful for Best after an SRS draft exists and before the team treats it as the source for architecture or coding and Buyers who want reusable AI-agent guidance instead of one-off prompts.
When this helps
What you get
- SRS review
- Change-control notes
- Traceability improvements
- Execution handoff
Use it when
- Use it when you already have a product brief or SRS draft, but are not sure it is clear enough to become the build contract.
- Use it when requirements still contain contradictions, missing acceptance criteria, unclear ownership, or casual edits.
- Use it when you need to lock what is actually approved before architecture, coding, UI, and QA inherit the same confusion.
Not the right fit when
- It improves and governs the SRS; it does not make business decisions the owner has not supplied.
What this prepares next
Stronger requirement source -> Less scope drift -> Cleaner downstream execution
Why this is stronger than asking AI once: A normal prompt can produce a useful answer once. This skill gives the buyer a repeatable workflow with checks, boundaries, and handoff evidence.
Who this is for
- Best after an SRS draft exists and before the team treats it as the source for architecture or coding.
- Buyers who want reusable AI-agent guidance instead of one-off prompts.
What this helps you improve
- Stronger requirement source
- Less scope drift
- Cleaner downstream execution
Included interface patterns
Main SRS Authority Map
Defines Main_SRS as the supreme project contract, with document structure, prefix policy, and governance rules.
Root SRS authority model and reading path.Modular SRS Governance
Plans child SRS modules, manifest entries, traceability, data mapping, changelog, and 400-line split gates.
Module registry, split plan, and traceability structure.Change-Control Decision
Reviews requirement changes for business validity, architecture fit, consistency, completeness, non-regression, and traceability.
ACCEPT, REJECT, or REQUEST CLARIFICATION decision with evidence. Workflow fit
Where this skill fits in the workflow.
This product belongs to the Requirements stage in the Vibe app builder roadmap. Use the roadmap to decide what to clarify first, which check should come next, and whether a connected workflow fits your current AI project problem better than a single skill.
Connected offer
Clarify My App Idea Bundle
Turn a vague app idea into clear scope, acceptance criteria, and architecture direction before build starts.
If two bundles include the same skill, the cart keeps it once and removes the duplicate from the estimate.