Guides users through defining features via adaptive discussion and generates structured feature 1-pagers. Use when users want to create a well-documented feature request or need help articulating a feature idea. The discussion is conversational, not a form - follow threads, ask follow-ups, and refine until the user is satisfied.
Guides users through adaptive feature discussions and generates structured 1-pagers for issue creation.
/plugin marketplace add kwiggen/claude-code-plugin/plugin install kwiggen-kw-plugin@kwiggen/claude-code-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Guide users through feature definition via adaptive discussion and generate lightweight feature 1-pagers.
Features should be defined through conversation, not forms. Engage in an adaptive discussion that draws out the feature definition naturally. The 1-pager is synthesized from this discussion.
Through natural conversation, understand these areas:
Problem Space:
User Impact:
Solution Vision:
Verbose users (provide lots of detail upfront):
Terse users (give minimal responses):
Uncertain users (don't have all answers):
After the discussion, synthesize a lightweight 1-pager:
# [Feature Name]
## Problem Statement
<2-3 sentences: What problem are we solving and why does it matter?>
## Proposed Solution
<High-level description of the approach. Focus on WHAT we're building, not HOW we'll implement it. 3-5 sentences.>
## Key Features
<Bullet list of the main capabilities this feature will provide>
- Feature capability 1
- Feature capability 2
- Feature capability 3
---
*Feature 1-pager generated with [Claude Code](https://claude.ai/code)*
When creating the 1-pager from the discussion:
After generating the 1-pager:
Display the complete 1-pager formatted in markdown
Ask for confirmation:
"Review this feature 1-pager. Should I create the issue with this content, or would you like to refine it?"
Handle responses:
No iteration limit - refine until the user is satisfied
Once the 1-pager is confirmed:
Prepare for issue creation:
Follow issue-creator patterns:
gh issue creategh project item-addUse heredoc for the body:
gh issue create --title "<feature-name>" --body "$(cat <<'EOF'
<1-pager-content>
EOF
)"
User: /create-feature User profile management
Claude: "Let's define this feature. What problem are you trying to solve with user profile management?"
User: "Users can't update their personal information after signing up. They have to contact support."
Claude: "That's frustrating. What kind of information do they typically want to update?"
User: "Name, email, profile picture. Sometimes notification preferences."
Claude: "Got it. Any constraints - like things they shouldn't be able to change?"
User: "Username and account type need to stay fixed."
Claude: "Makes sense. Let me put together a 1-pager based on our discussion."
(Generates 1-pager)
# User Profile Management
## Problem Statement
Users cannot update their personal information after initial signup, requiring them to contact support for simple changes. This creates friction and generates unnecessary support volume.
## Proposed Solution
Provide a self-service profile management interface where users can update their name, email, profile picture, and notification preferences. Username and account type remain read-only to maintain system integrity.
## Key Features
- Update name and display name
- Change email address (with verification)
- Upload and manage profile picture
- Configure notification preferences
- View but not edit username and account type
---
*Feature 1-pager generated with [Claude Code](https://claude.ai/code)*
Claude: "Review this feature 1-pager. Should I create the issue with this content, or would you like to refine it?"
User: "Add password reset to key features"
Claude: (Updates 1-pager and shows again)
User: "Looks good, create it"
Claude: (Proceeds to create issue via issue-creator patterns)
If user indicates they want to stop:
Understood. We can resume the feature definition anytime with /create-feature.
If discussion didn't cover something and you can't infer:
## [Section]
*TBD - needs further discussion*
Ask user to provide more details during review.
In Discussion:
In 1-Pager: