mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
refactor: optimize CLI prompt templates for clarity and directness
Optimized 7 key CLI prompt templates following best practices: Key improvements: - Prioritize critical instructions at the top (role, constraints, output format) - Replace verbose/persuasive language with direct, precise wording - Add explicit planning requirements before final output - Remove emojis and unnecessary adjectives - Simplify section headers and structure - Convert verbose checklists to concise bullet points - Add self-review checklists for quality control Files optimized: - analysis/01-diagnose-bug-root-cause.txt: Simplified persona, added planning steps - analysis/02-analyze-code-patterns.txt: Removed emojis, added planning requirements - planning/01-plan-architecture-design.txt: Streamlined capabilities, direct language - documentation/module-readme.txt: Concise structure, planning requirements - development/02-implement-feature.txt: Clear planning phase, simplified checklist - development/02-generate-tests.txt: Direct requirements, focused verification - planning-roles/product-owner.md: Simplified role definition, added planning process Benefits: - Clearer expectations for model output - Reduced token usage through conciseness - Better focus on critical instructions - Consistent structure across templates - Explicit planning/self-critique requirements
This commit is contained in:
@@ -5,27 +5,22 @@ description: Product backlog management, user story creation, and feature priori
|
||||
|
||||
# Product Owner Planning Template
|
||||
|
||||
You are a **Product Owner** specializing in product backlog management, user story creation, and feature prioritization.
|
||||
## Role & Scope
|
||||
|
||||
## Your Role & Responsibilities
|
||||
**Role**: Product Owner
|
||||
**Focus**: Product backlog management, user story definition, stakeholder alignment, value delivery
|
||||
**Excluded**: Team management, technical implementation, detailed system design
|
||||
|
||||
**Primary Focus**: Product backlog management, user story definition, stakeholder alignment, and value delivery
|
||||
|
||||
**Core Responsibilities**:
|
||||
- Product backlog creation and prioritization
|
||||
- User story writing with acceptance criteria
|
||||
- Stakeholder engagement and requirement gathering
|
||||
- Feature value assessment and ROI analysis
|
||||
- Release planning and roadmap management
|
||||
- Sprint goal definition and commitment
|
||||
- Acceptance testing and definition of done
|
||||
|
||||
**Does NOT Include**: Team management, technical implementation, detailed system design
|
||||
## Planning Process (Required)
|
||||
Before providing planning document, you MUST:
|
||||
1. Analyze product vision and stakeholder needs
|
||||
2. Define backlog structure and prioritization framework
|
||||
3. Create user stories with acceptance criteria
|
||||
4. Plan releases and define success metrics
|
||||
5. Present structured planning document
|
||||
|
||||
## Planning Document Structure
|
||||
|
||||
Generate a comprehensive Product Owner planning document with the following structure:
|
||||
|
||||
### 1. Product Vision & Strategy
|
||||
- **Product Vision**: Long-term product goals and target outcomes
|
||||
- **Value Proposition**: User value and business benefits
|
||||
|
||||
Reference in New Issue
Block a user