Create implementation-ready plans with verbatim prompts and optional GitHub issues.
npx skills add https://github.com/gparker97/beanies-family --skill beanies-plan
Please help me install this Agent Skill. Skill: beanies-plan Source: https://github.com/gparker97/beanies-family/tree/main/.claude/skills/beanies-plan Command: npx skills add https://github.com/gparker97/beanies-family --skill beanies-plan
This Skill prevents knowledge loss and ambiguity during feature planning by capturing the full conversational context, decisions, and assumptions so work can be implemented later without additional clarification.
Ask the skill to create a plan for your requested feature, answer any clarifying questions it asks, and indicate whether to create a GitHub issue.
High-intent search queries and answers about installing and using this skill.
Capturing full conversational context for developer handoffs requires recording verbatim prompts and iterations, then saving approved plans to docs/plans or optionally creating GitHub issues with complete prompt logs attached.
Yes, generating GitHub issues with full prompt logs from feature planning conversations is supported. After explicit approval, the skill creates issues containing a complete prompt log comment that records every iteration and decision.
Documenting feature requirements and iteration history for engineering tickets is best handled through clarification-driven drafting that iterates until explicit approval, ensuring all assumptions and verbatim follow-up messages are preserved in the final plan.
A GitHub repository setup is not required to use this planning and documentation workflow. You can save approved plans directly to docs/plans locally, and only need GitHub integration if you choose to create issues for developer handoffs.
Approved implementation plans are stored in the docs/plans directory. This persistent, auditable location ensures full context and decisions remain accessible for future implementation without requiring additional clarification.
Clarification-driven drafting improves feature planning outcomes by asking necessary clarifying questions and iterating the plan until explicit approval is given, preventing knowledge loss and ambiguity before any implementation work begins.
rnwolfeConvert rough ideas into structured GitHub issues with labels and approval.
troykellyCreate or validate GitHub issues with acceptance criteria and project board links.
luanzebaPlan and organize GitHub issues with types, dependencies, and sub-issues.
tomturingAutomate project iteration workflows from requirement analysis to PR merge.
