Use this skill for early-stage project planning. It leverages the Gemini CLI to generate high-quality first drafts of Product Briefs, Research Documents, and full PRDs, guiding users from idea to validated requirements. Triggers include "create PRD", "product brief", or "validate requirements".
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin bodangren-git-workflowThis skill uses the workspace's default tool permissions.
To accelerate and enhance early-stage project planning by using a powerful generative AI to create high-quality first drafts of key strategic documents. This skill integrates the Gemini CLI into the PRD authoring workflow, transforming it from a manual template-filling exercise into a dynamic, AI-assisted process.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
To accelerate and enhance early-stage project planning by using a powerful generative AI to create high-quality first drafts of key strategic documents. This skill integrates the Gemini CLI into the PRD authoring workflow, transforming it from a manual template-filling exercise into a dynamic, AI-assisted process.
The skill guides users from a vague project idea to a well-defined Product Requirements Document (PRD) by:
This approach bridges the gap between "we have an idea" and "we're ready to write specs" with unprecedented speed and quality.
Use this skill in the following situations:
Do NOT use this skill for:
docs/ directory exists).gemini CLI tool installed and authenticated.Strategy Before Tactics: PRDs define WHAT we're building and WHY before specs define HOW we'll build it. This skill uses AI to rapidly generate the "WHAT" and "WHY" so that teams can focus on review, refinement, and strategic alignment.
status CommandAssess project readiness and provide guidance on next workflow steps. This is the recommended starting point.
Run the status check to understand the current state of your PRD documents.
bash scripts/prd-authoring.sh status [project-name]
The script will report which documents exist (product-brief.md, research.md, prd.md, etc.) and recommend the next logical command to run.
brief CommandGenerate a comprehensive, high-quality first draft of a Product Brief from a simple project name.
Execute the script with your project name.
bash scripts/prd-authoring.sh brief "Your Awesome Project Name"
Instead of creating an empty template, the script calls the Gemini CLI with a detailed prompt, asking it to generate a full product brief. This includes plausible, well-structured content for:
The output from Gemini is saved as the first draft in docs/prds/your-awesome-project-name/product-brief.md.
Open the generated file. Review the AI-generated content with your team and stakeholders, refining the details to match your specific vision. The draft provides a strong foundation, saving hours of initial writing.
research CommandGenerate a targeted, context-aware market research plan based on the contents of your product brief.
Once your product brief is reviewed and saved, run the research command:
bash scripts/prd-authoring.sh research your-awesome-project-name
The script sends the entire content of your product-brief.md to the Gemini CLI. It prompts the AI to act as a business analyst and generate a research plan that logically follows from the brief. The generated draft will include sections for:
This draft is saved to docs/prds/your-awesome-project-name/research.md.
Use the AI-generated document as a guide for your research activities. Fill in the details and refine the analysis based on your actual findings.
create-prd CommandGenerate a comprehensive, detailed first draft of a Product Requirements Document (PRD) by synthesizing the product brief and the research document.
After completing your brief and research documents, run the create-prd command:
bash scripts/prd-authoring.sh create-prd your-awesome-project-name
This is the most powerful feature. The script sends the full content of both your product brief and your research document to the Gemini CLI. It prompts the AI to generate a detailed PRD that includes:
The resulting draft, saved in docs/prds/your-awesome-project-name/prd.md, is a deeply contextualized document that connects business goals from the brief with insights from the research.
The generated PRD provides an excellent starting point. Review it with your team to ensure all requirements are accurate, testable, and aligned with project goals. Use the validate-prd command to check for quality.
validate-prd CommandValidate an existing PRD against quality standards, checking for missing sections, vague requirements, and unmeasurable success criteria. This command does not use the Gemini CLI; it uses pattern matching to enforce quality.
Run the validation check on your PRD:
bash scripts/prd-authoring.sh validate-prd your-awesome-project-name
Review the report and address any issues found.
decompose CommandBreak down a validated PRD into epics for sprint planning. This helps transition from strategic planning to tactical execution.
Once your PRD is validated, run the decompose command:
bash scripts/prd-authoring.sh decompose your-awesome-project-name
This creates an epics.md file with a template structure for you to define your epics.
Symptom: The script fails during the brief, research, or create-prd commands with an error related to the gemini command.
Solution:
gemini CLI is installed and in your system's PATH.gemini auth if needed.prd-authoring.sh script for any potential issues.For issues related to file existence, permissions, or validation errors, the script provides detailed error messages and recommendations. Always check the script's output for guidance.
research and prd documents depends on the quality of the product-brief you provide. Take time to refine the initial brief.status command to guide you through the workflow. Don't be afraid to go back and refine a previous document if new insights emerge.