Requirement trace is handled by this skill in a buyer-readable, reusable workflow.
Scope discipline is handled by this skill in a buyer-readable, reusable workflow.
SB_srs_executor@SB_srs_executorAgent SetupLevel 2 Guided Skill15 minutes
What is this?
A paid implementation-discipline skill that makes an AI agent execute accepted SRS requirements with traceable tasks, evidence, and scope control. Build from the approved Software Requirements Specification instead of letting implementation drift with the latest chat instruction. Use it when you need help with Use it when requirements are already approved and you need AI to build from them instead of drifting with the latest chat instruction and Use it when working code is not enough, because you still need to know which requirement each change satisfies. Without it, teams usually keep suffering through Less build drift and Clearer requirement coverage. The buyer can use it to produce Requirement-to-task plan and Implementation notes with a clearer next step and less prompt guesswork. It is especially useful for Best when the SRS is accepted and the team is ready to implement without reopening basic product scope every few minutes and Buyers who want reusable AI-agent guidance instead of one-off prompts.
When this helps
What you get
- Requirement-to-task plan
- Implementation notes
- Evidence log
- Residual risk report
Use it when
- Use it when requirements are already approved and you need AI to build from them instead of drifting with the latest chat instruction.
- Use it when working code is not enough, because you still need to know which requirement each change satisfies.
- Use it when you want implementation tasks, evidence, and remaining risks tied back to the accepted product scope.
Not the right fit when
- It should not be used when requirements are still unstable. First stabilize the SRS with the creator/governor path.
What this prepares next
Less build drift -> Clearer requirement coverage -> Better release evidence
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 when the SRS is accepted and the team is ready to implement without reopening basic product scope every few minutes.
- Buyers who want reusable AI-agent guidance instead of one-off prompts.
What this helps you improve
- Less build drift
- Clearer requirement coverage
- Better release evidence
Included interface patterns
Requirement Lock
Confirms accepted Requirement IDs, SRS sources, acceptance criteria, scope, and verification before implementation.
Requirement lock and scoped SRS reading log.Traceable Implementation Plan
Maps each acceptance criterion to planned files, linked skill gates, and verification evidence.
Requirement-to-task table and linked governor handoff blocks.Verified Code Handoff
Reports files changed, Requirement IDs, tests, manual checks, task evidence, and residual risks.
SRS Executor Result ready for project review. Workflow fit
Where this skill fits in the workflow.
This product belongs to the Build and clean code 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
Review My AI-Built MVP Bundle
Review implementation, interface, code quality, and security risk before trusting an AI-built MVP.
If two bundles include the same skill, the cart keeps it once and removes the duplicate from the estimate.