Guide users through clarifying ambiguous requirements and submitting PRDs to GitHub.
npx skills add https://github.com/ai-native-camp/camp-2 --skill day3-clarify
Please help me install this Agent Skill. Skill: day3-clarify Source: https://github.com/ai-native-camp/camp-2/tree/main/.claude/skills/day3-clarify Command: npx skills add https://github.com/ai-native-camp/camp-2 --skill day3-clarify
This Skill transforms vague requirements into actionable specifications, empowers you to build custom AI skills, and guides you through submitting your first Product Requirements Document (PRD) to GitHub.
clarify:vague and clarify:unknown skills to turn ambiguous requests into clear, structured specifications via interactive questioning.clarify skill based on your specific workflow using provided templates.Use the day3-clarify skill to start clarifying your requirements and building your first PRD for GitHub submission.
High-intent search queries and answers about installing and using this skill.
You clarify ambiguous requirements for AI development by using interactive AI-driven questioning to transform vague requests into structured, actionable specifications. This process ensures unclear project details are resolved before technical implementation begins.
To create and submit a PRD to GitHub, you generate the document from clarified specifications and use GitHub CLI for automated Pull Request creation. This guides your custom skill directly into your personal repository as a structured proposal.
Yes, you can build custom AI skills for your specific workflow using provided templates. The process guides you to create a personalized clarify skill based on your unique requirements, ensuring the AI aligns with your operational needs.
Yes, you need GitHub CLI installed to automate PRD pull requests. The Skill integrates directly with GitHub CLI to automatically create Pull Requests for your Product Requirements Documents, requiring this command-line tool for repository submission.
The difference between clarify vague and clarify unknown processing lies in their target input: clarify vague transforms imprecise requests into structured specifications, while clarify unknown resolves missing context. Both use interactive questioning to achieve actionable requirement clarity.
GitnappConfigure GitHub authentication via tokens, SSH keys, or gh CLI.
oxieAutomate staging deployment with auto-merge for merged pull requests.
onbluerosesConvert product requirement documents into GitHub issues via vertical slices.
silaslopes100Identify and resolve ambiguities in project requirement documents through gap analysis and user questioning.