Generate PRD, SRD, SDD, API Spec, and Dev Plan documents.
npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-spec
Please help me install this Agent Skill. Skill: vibe-sdlc-spec Source: https://github.com/robin-li/vibe-money-book/tree/main/.claude/skills/vibe-sdlc-spec Command: npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-spec
This Skill helps teams define a Single Source of Truth for project specifications by guiding the creation and cross-checking of PRD, SRD, SDD, API Spec, and Dev Plan using AI-assisted drafting and quality checks.
Describe your project scope and goals, and I will generate an initial SDLC specification draft.
High-intent search queries and answers about installing and using this skill.
AI-guided SDLC specification workflows produce PRD, SRD, SDD, API Spec, and Dev Plan artifacts by drafting initial documents from your project scope and goals. This enforces a single source of truth for early project initialization and stakeholder alignment.
Applying automated cross-review and integrity validation across your SDLC spec documents ensures consistency. This performs automated gap detection to check alignment between requirements, architecture, and API contracts.
You create a single source of truth by orchestrating an AI-driven SDLC specification workflow that cross-checks PRD, SRD, SDD, and API Spec documents. This enforces alignment among stakeholders during early project initialization.
Yes, you can customize the SDLC specification workflow by incorporating optional scripts, references, and assets directories. This tailors the AI-assisted drafting and quality check process to your specific project requirements.
You need an AI-guided SDLC specification process during early project initialization to establish alignment among stakeholders. It is essential when you must enforce quality checks across requirements, architecture, and API contracts before development begins.
Yes, the SDLC spec workflow enforces YAML frontmatter in generated documents for automated discovery. This metadata structure ensures that PRD, SRD, SDD, and API Spec files are properly indexed and managed within the system.
cshyangPlan and execute a project discovery phase to define requirements and scope.
robin-liConvert finalized development plans into GitHub Issues and linked project boards.
26mitch26Merge pull requests, deploy changes, and verify production health via CI/CD pipelines.
loanntcGenerate BRD, FRD, and SRD documents with testable requirements and traceability.
