@dedesfr/prompter 0.4.0 → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/.github/prompts/product-brief.prompt.md +81 -38
  2. package/dist/cli/index.js +1 -1
  3. package/dist/core/templates/slash-command-templates.d.ts.map +1 -1
  4. package/dist/core/templates/slash-command-templates.js +81 -38
  5. package/dist/core/templates/slash-command-templates.js.map +1 -1
  6. package/package.json +1 -1
  7. package/prompt/product-brief.md +239 -34
  8. package/src/cli/index.ts +1 -1
  9. package/src/core/templates/slash-command-templates.ts +81 -38
package/.github/prompts/product-brief.prompt.md CHANGED
@@ -7,7 +7,7 @@ $ARGUMENTS
7
7
  You are a Senior Product Manager with 15+ years of experience crafting executive-level product briefs for Fortune 500 companies. You excel at distilling complex product information into clear, compelling summaries that drive stakeholder alignment and decision-making.
8
8
 
9
9
  # Context
10
- You are creating a Product Brief (Executive Summary) - a concise, high-impact document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders who need to quickly understand the product's value proposition, market opportunity, and strategic fit.
10
+ You are creating a Product Brief (Executive Summary) - a comprehensive, visually-rich document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders. The document should be scannable, use tables for structured data, and include visual elements where appropriate.
11
11
 
12
12
  # Primary Objective
13
13
  Generate a polished, professional Product Brief that captures the essence of the product in a format suitable for executive review, board presentations, or investor communications.
@@ -23,77 +23,120 @@ Provide any combination of the following:
23
23
  - Current status/stage
24
24
  - Key metrics or traction (if available)
25
25
  - Strategic goals
26
+ - Technical stack (if applicable)
27
+ - User roles
26
28
 
27
29
  *Note: Work with whatever information is provided; make reasonable inferences for gaps while flagging assumptions.*
28
30
 
29
31
  # Output Format
30
32
 
31
- ## [PRODUCT NAME] - Executive Summary
33
+ The output should follow this comprehensive structure:
32
34
 
33
- ### The Opportunity
34
- [2-3 sentences describing the market problem and opportunity size]
35
+ ## 1. Header Section
36
+ ```markdown
37
+ # [PRODUCT NAME]
38
+ ## Executive Summary
35
39
 
36
- ### Our Solution
37
- [2-3 sentences on what the product does and its core value proposition]
40
+ **[One-line tagline describing what the product is]**
38
41
 
39
- ### Target Customer
40
- [Specific customer segment with key characteristics]
42
+ ---
41
43
 
42
- ### Key Differentiators
43
- - [Differentiator 1]
44
- - [Differentiator 2]
45
- - [Differentiator 3]
44
+ ## At a Glance
46
45
 
47
- ### Business Model
48
- [1-2 sentences on how the product generates revenue]
46
+ | | |
47
+ | ----------------- | ---------------------------------------- |
48
+ | **Product Type** | [Category/type of product] |
49
+ | **Target Market** | [Primary target market/segment] |
50
+ | **Platform** | [Web/Mobile/Desktop/API/etc.] |
51
+ | **Technology** | [Key technology stack - if applicable] |
52
+ | **Status** | [Current development/market status] |
53
+ ```
49
54
 
50
- ### Traction & Validation
51
- [Key metrics, milestones, or validation points - use "Target:" prefix for projections]
55
+ ## 2. Product Overview
56
+ - "What is [Product Name]?" section with 2-3 sentences
57
+ - "The Problem We Solve" table (Challenge | Impact)
58
+ - "Our Solution" with ASCII flow diagram
52
59
 
53
- ### Competitive Position
54
- [Brief competitive landscape and positioning statement]
60
+ ## 3. Core Capabilities
61
+ - Numbered sections (1️⃣, 2️⃣, 3️⃣, etc.) with bullet points
62
+ - Typically 3-6 capability categories
55
63
 
56
- ### Strategic Fit
57
- [How this aligns with broader company/market strategy]
64
+ ## 4. Key Benefits
65
+ - Table format with emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄)
66
+ - Benefit name | Description
58
67
 
59
- ### Ask / Next Steps
60
- [Clear call-to-action or decision needed]
68
+ ## 5. User Roles Supported
69
+ - Table: Role | Primary Functions
61
70
 
62
- ---
63
- **Status:** [Current stage]
64
- **Owner:** [Product lead/team]
65
- **Last Updated:** [Date]
71
+ ## 6. System Architecture / Modules
72
+ - ASCII box diagram showing module structure
73
+ - Summary of module count
74
+
75
+ ## 7. Infrastructure Highlights
76
+ - Bullet points with bold headers
77
+
78
+ ## 8. Domain-Specific Features
79
+ - Subsections with checkmarks (✅)
80
+ - Workflow diagrams using arrows (→)
81
+
82
+ ## 9. Dashboard / Analytics
83
+ - Table: Widget | Purpose
84
+
85
+ ## 10. Competitive Advantages
86
+ - Comparison table: Feature | [Product] | Traditional Methods
87
+ - Use ✅ for advantages, ❌ for competitor disadvantages
88
+
89
+ ## 11. Roadmap Considerations
90
+ - Current State (bullet points)
91
+ - Potential Enhancements table (Priority | Enhancement)
92
+
93
+ ## 12. Technical Foundation
94
+ - Table: Component | Choice | Why
95
+
96
+ ## 13. Getting Started
97
+ - For New Implementations (numbered steps)
98
+ - For Existing Users (bullet points)
99
+
100
+ ## 14. Summary
101
+ - "[Product Name] transforms [domain] by:" followed by numbered benefits
102
+
103
+ ## 15. Document Information
104
+ - Table with Version, Date, Classification, Full Specification reference
66
105
 
67
106
  # Writing Standards
68
107
  - **Tone:** Confident, data-informed, strategic
69
- - **Length:** 1 page maximum (300-500 words)
108
+ - **Length:** Comprehensive but scannable (typically 200-400 lines)
70
109
  - **Language:** Executive-friendly, minimal jargon
71
- - **Numbers:** Include quantified metrics wherever possible
72
- - **Clarity:** Each section should be understandable in isolation
110
+ - **Visuals:** Use tables for structured data, ASCII diagrams for flows/architecture
111
+ - **Icons:** Use emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄, 1️⃣, 2️⃣, etc.) to improve scannability
112
+ - **Checkmarks:** Use ✅ for features/advantages, ❌ for competitor disadvantages
73
113
 
74
114
  # Quality Criteria
75
- 1. A busy executive can understand the product in under 2 minutes
76
- 2. The value proposition is immediately clear
77
- 3. Key decisions or asks are explicit
78
- 4. Claims are specific and quantified where possible
79
- 5. Strategic rationale is evident
115
+ 1. A busy executive can understand the product in under 5 minutes
116
+ 2. The value proposition is immediately clear from the first sections
117
+ 3. Tables make data comparison easy and quick to scan
118
+ 4. Visual diagrams help explain system architecture and workflows
119
+ 5. Competitive positioning is explicit and easy to understand
120
+ 6. Technical and non-technical stakeholders can both extract value
80
121
 
81
122
  # Special Instructions
82
- - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION]
123
+ - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION] or use placeholder text like [TBD]
83
124
  - Prioritize clarity over comprehensiveness
84
125
  - Lead with impact, not features
85
126
  - Use active voice and strong verbs
86
127
  - Avoid superlatives without supporting data
87
128
  - If competitive information is sparse, focus on unique value rather than comparisons
129
+ - Adapt section headers to match the product domain (e.g., "Financial Features" for fintech, "Clinical Workflow" for healthcare)
130
+ - Skip sections that don't apply to the product type (e.g., "Technical Foundation" for non-software products)
88
131
 
89
132
  ## WORKFLOW STEPS
90
133
  1. Read the user's input about the product
91
134
  2. Generate a unique, URL-friendly slug from the product name (lowercase, hyphen-separated)
92
- 3. Create the directory `prompter/<slug>/` if it doesn't exist
135
+ 3. Create the directory \`prompter/<slug>/\` if it doesn't exist
93
136
  4. Generate the complete Product Brief following all requirements above
94
- 5. Save the Product Brief to `prompter/<slug>/product-brief.md`
137
+ 5. Save the Product Brief to \`prompter/<slug>/product-brief.md\`
95
138
  6. Report the saved file path
96
139
 
97
140
  ## REFERENCE
98
- - Read `prompter/project.md` for project context if needed
141
+ - Read \`prompter/project.md\` for project context if needed
99
142
  <!-- prompter-managed-end -->
package/dist/cli/index.js CHANGED
@@ -7,7 +7,7 @@ const program = new Command();
7
7
  program
8
8
  .name('prompter')
9
9
  .description('Enhance prompts directly in your AI coding workflow')
10
- .version('0.4.0');
10
+ .version('0.4.1');
11
11
  program
12
12
  .command('init')
13
13
  .description('Initialize Prompter in your project')
package/dist/core/templates/slash-command-templates.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"slash-command-templates.d.ts","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,cAAc,GAAG,SAAS,GAAG,eAAe,GAAG,eAAe,GAAG,aAAa,GAAG,cAAc,GAAG,kBAAkB,GAAG,eAAe,CAAC;AAiyBnJ,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,cAAc,EAAE,MAAM,CAQ7D,CAAC;AAEF,wBAAgB,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM,CAE9D;AAED,qBAAa,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM;CAGzD"}
1
+ {"version":3,"file":"slash-command-templates.d.ts","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,cAAc,GAAG,SAAS,GAAG,eAAe,GAAG,eAAe,GAAG,aAAa,GAAG,cAAc,GAAG,kBAAkB,GAAG,eAAe,CAAC;AA40BnJ,eAAO,MAAM,kBAAkB,EAAE,MAAM,CAAC,cAAc,EAAE,MAAM,CAQ7D,CAAC;AAEF,wBAAgB,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM,CAE9D;AAED,qBAAa,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAE,EAAE,cAAc,GAAG,MAAM;CAGzD"}
package/dist/core/templates/slash-command-templates.js CHANGED
@@ -701,7 +701,7 @@ const productBriefWorkflow = `# Role & Expertise
701
701
  You are a Senior Product Manager with 15+ years of experience crafting executive-level product briefs for Fortune 500 companies. You excel at distilling complex product information into clear, compelling summaries that drive stakeholder alignment and decision-making.
702
702
 
703
703
  # Context
704
- You are creating a Product Brief (Executive Summary) - a concise, high-impact document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders who need to quickly understand the product's value proposition, market opportunity, and strategic fit.
704
+ You are creating a Product Brief (Executive Summary) - a comprehensive, visually-rich document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders. The document should be scannable, use tables for structured data, and include visual elements where appropriate.
705
705
 
706
706
  # Primary Objective
707
707
  Generate a polished, professional Product Brief that captures the essence of the product in a format suitable for executive review, board presentations, or investor communications.
@@ -717,79 +717,122 @@ Provide any combination of the following:
717
717
  - Current status/stage
718
718
  - Key metrics or traction (if available)
719
719
  - Strategic goals
720
+ - Technical stack (if applicable)
721
+ - User roles
720
722
 
721
723
  *Note: Work with whatever information is provided; make reasonable inferences for gaps while flagging assumptions.*
722
724
 
723
725
  # Output Format
724
726
 
725
- ## [PRODUCT NAME] - Executive Summary
727
+ The output should follow this comprehensive structure:
726
728
 
727
- ### The Opportunity
728
- [2-3 sentences describing the market problem and opportunity size]
729
+ ## 1. Header Section
730
+ \`\`\`markdown
731
+ # [PRODUCT NAME]
732
+ ## Executive Summary
729
733
 
730
- ### Our Solution
731
- [2-3 sentences on what the product does and its core value proposition]
734
+ **[One-line tagline describing what the product is]**
732
735
 
733
- ### Target Customer
734
- [Specific customer segment with key characteristics]
736
+ ---
735
737
 
736
- ### Key Differentiators
737
- - [Differentiator 1]
738
- - [Differentiator 2]
739
- - [Differentiator 3]
738
+ ## At a Glance
740
739
 
741
- ### Business Model
742
- [1-2 sentences on how the product generates revenue]
740
+ | | |
741
+ | ----------------- | ---------------------------------------- |
742
+ | **Product Type** | [Category/type of product] |
743
+ | **Target Market** | [Primary target market/segment] |
744
+ | **Platform** | [Web/Mobile/Desktop/API/etc.] |
745
+ | **Technology** | [Key technology stack - if applicable] |
746
+ | **Status** | [Current development/market status] |
747
+ \`\`\`
743
748
 
744
- ### Traction & Validation
745
- [Key metrics, milestones, or validation points - use "Target:" prefix for projections]
749
+ ## 2. Product Overview
750
+ - "What is [Product Name]?" section with 2-3 sentences
751
+ - "The Problem We Solve" table (Challenge | Impact)
752
+ - "Our Solution" with ASCII flow diagram
746
753
 
747
- ### Competitive Position
748
- [Brief competitive landscape and positioning statement]
754
+ ## 3. Core Capabilities
755
+ - Numbered sections (1️⃣, 2️⃣, 3️⃣, etc.) with bullet points
756
+ - Typically 3-6 capability categories
749
757
 
750
- ### Strategic Fit
751
- [How this aligns with broader company/market strategy]
758
+ ## 4. Key Benefits
759
+ - Table format with emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄)
760
+ - Benefit name | Description
752
761
 
753
- ### Ask / Next Steps
754
- [Clear call-to-action or decision needed]
762
+ ## 5. User Roles Supported
763
+ - Table: Role | Primary Functions
755
764
 
756
- ---
757
- **Status:** [Current stage]
758
- **Owner:** [Product lead/team]
759
- **Last Updated:** [Date]
765
+ ## 6. System Architecture / Modules
766
+ - ASCII box diagram showing module structure
767
+ - Summary of module count
768
+
769
+ ## 7. Infrastructure Highlights
770
+ - Bullet points with bold headers
771
+
772
+ ## 8. Domain-Specific Features
773
+ - Subsections with checkmarks (✅)
774
+ - Workflow diagrams using arrows (→)
775
+
776
+ ## 9. Dashboard / Analytics
777
+ - Table: Widget | Purpose
778
+
779
+ ## 10. Competitive Advantages
780
+ - Comparison table: Feature | [Product] | Traditional Methods
781
+ - Use ✅ for advantages, ❌ for competitor disadvantages
782
+
783
+ ## 11. Roadmap Considerations
784
+ - Current State (bullet points)
785
+ - Potential Enhancements table (Priority | Enhancement)
786
+
787
+ ## 12. Technical Foundation
788
+ - Table: Component | Choice | Why
789
+
790
+ ## 13. Getting Started
791
+ - For New Implementations (numbered steps)
792
+ - For Existing Users (bullet points)
793
+
794
+ ## 14. Summary
795
+ - "[Product Name] transforms [domain] by:" followed by numbered benefits
796
+
797
+ ## 15. Document Information
798
+ - Table with Version, Date, Classification, Full Specification reference
760
799
 
761
800
  # Writing Standards
762
801
  - **Tone:** Confident, data-informed, strategic
763
- - **Length:** 1 page maximum (300-500 words)
802
+ - **Length:** Comprehensive but scannable (typically 200-400 lines)
764
803
  - **Language:** Executive-friendly, minimal jargon
765
- - **Numbers:** Include quantified metrics wherever possible
766
- - **Clarity:** Each section should be understandable in isolation
804
+ - **Visuals:** Use tables for structured data, ASCII diagrams for flows/architecture
805
+ - **Icons:** Use emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄, 1️⃣, 2️⃣, etc.) to improve scannability
806
+ - **Checkmarks:** Use ✅ for features/advantages, ❌ for competitor disadvantages
767
807
 
768
808
  # Quality Criteria
769
- 1. A busy executive can understand the product in under 2 minutes
770
- 2. The value proposition is immediately clear
771
- 3. Key decisions or asks are explicit
772
- 4. Claims are specific and quantified where possible
773
- 5. Strategic rationale is evident
809
+ 1. A busy executive can understand the product in under 5 minutes
810
+ 2. The value proposition is immediately clear from the first sections
811
+ 3. Tables make data comparison easy and quick to scan
812
+ 4. Visual diagrams help explain system architecture and workflows
813
+ 5. Competitive positioning is explicit and easy to understand
814
+ 6. Technical and non-technical stakeholders can both extract value
774
815
 
775
816
  # Special Instructions
776
- - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION]
817
+ - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION] or use placeholder text like [TBD]
777
818
  - Prioritize clarity over comprehensiveness
778
819
  - Lead with impact, not features
779
820
  - Use active voice and strong verbs
780
821
  - Avoid superlatives without supporting data
781
822
  - If competitive information is sparse, focus on unique value rather than comparisons
823
+ - Adapt section headers to match the product domain (e.g., "Financial Features" for fintech, "Clinical Workflow" for healthcare)
824
+ - Skip sections that don't apply to the product type (e.g., "Technical Foundation" for non-software products)
782
825
 
783
826
  ## WORKFLOW STEPS
784
827
  1. Read the user's input about the product
785
828
  2. Generate a unique, URL-friendly slug from the product name (lowercase, hyphen-separated)
786
- 3. Create the directory \`prompter/<slug>/\` if it doesn't exist
829
+ 3. Create the directory \\\`prompter/<slug>/\\\` if it doesn't exist
787
830
  4. Generate the complete Product Brief following all requirements above
788
- 5. Save the Product Brief to \`prompter/<slug>/product-brief.md\`
831
+ 5. Save the Product Brief to \\\`prompter/<slug>/product-brief.md\\\`
789
832
  6. Report the saved file path
790
833
 
791
834
  ## REFERENCE
792
- - Read \`prompter/project.md\` for project context if needed`;
835
+ - Read \\\`prompter/project.md\\\` for project context if needed`;
793
836
  export const slashCommandBodies = {
794
837
  enhance: enhanceWorkflow,
795
838
  'prd-generator': prdGeneratorWorkflow,
package/dist/core/templates/slash-command-templates.js.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"slash-command-templates.js","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAEA,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEAyC2C,CAAC;AAEpE,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA6MgC,CAAC;AAE9D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAyDkC,CAAC;AAE9D,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAgFiC,CAAC;AAE9D,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA+I8B,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAuKgC,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA4FgC,CAAC;AAE9D,MAAM,CAAC,MAAM,kBAAkB,GAAmC;IAC9D,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,oBAAoB;IACrC,eAAe,EAAE,oBAAoB;IACrC,aAAa,EAAE,kBAAkB;IACjC,cAAc,EAAE,mBAAmB;IACnC,kBAAkB,EAAE,sBAAsB;IAC1C,eAAe,EAAE,oBAAoB;CACxC,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,EAAkB;IAClD,OAAO,kBAAkB,CAAC,EAAE,CAAC,CAAC;AAClC,CAAC;AAED,MAAM,OAAO,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAkB;QACzC,OAAO,mBAAmB,CAAC,EAAE,CAAC,CAAC;IACnC,CAAC;CACJ"}
1
+ {"version":3,"file":"slash-command-templates.js","sourceRoot":"","sources":["../../../src/core/templates/slash-command-templates.ts"],"names":[],"mappings":"AAEA,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;mEAyC2C,CAAC;AAEpE,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA6MgC,CAAC;AAE9D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAyDkC,CAAC;AAE9D,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAgFiC,CAAC;AAE9D,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DA+I8B,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6DAuKgC,CAAC;AAE9D,MAAM,oBAAoB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iEAuIoC,CAAC;AAElE,MAAM,CAAC,MAAM,kBAAkB,GAAmC;IAC9D,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,oBAAoB;IACrC,eAAe,EAAE,oBAAoB;IACrC,aAAa,EAAE,kBAAkB;IACjC,cAAc,EAAE,mBAAmB;IACnC,kBAAkB,EAAE,sBAAsB;IAC1C,eAAe,EAAE,oBAAoB;CACxC,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,EAAkB;IAClD,OAAO,kBAAkB,CAAC,EAAE,CAAC,CAAC;AAClC,CAAC;AAED,MAAM,OAAO,eAAe;IACxB,MAAM,CAAC,mBAAmB,CAAC,EAAkB;QACzC,OAAO,mBAAmB,CAAC,EAAE,CAAC,CAAC;IACnC,CAAC;CACJ"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dedesfr/prompter",
3
- "version": "0.4.0",
3
+ "version": "0.4.1",
4
4
  "description": "Enhance prompts directly in your AI coding workflow",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
package/prompt/product-brief.md CHANGED
@@ -4,7 +4,7 @@
4
4
  You are a Senior Product Manager with 15+ years of experience crafting executive-level product briefs for Fortune 500 companies. You excel at distilling complex product information into clear, compelling summaries that drive stakeholder alignment and decision-making.
5
5
 
6
6
  # Context
7
- You are creating a Product Brief (Executive Summary) - a concise, high-impact document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders who need to quickly understand the product's value proposition, market opportunity, and strategic fit.
7
+ You are creating a Product Brief (Executive Summary) - a comprehensive, visually-rich document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders. The document should be scannable, use tables for structured data, and include visual elements where appropriate.
8
8
 
9
9
  # Primary Objective
10
10
  Generate a polished, professional Product Brief that captures the essence of the product in a format suitable for executive review, board presentations, or investor communications.
@@ -20,65 +20,270 @@ Provide any combination of the following:
20
20
  - Current status/stage
21
21
  - Key metrics or traction (if available)
22
22
  - Strategic goals
23
+ - Technical stack (if applicable)
24
+ - User roles
23
25
 
24
26
  *Note: Work with whatever information is provided; make reasonable inferences for gaps while flagging assumptions.*
25
27
 
26
28
  # Output Format
27
29
 
28
- ## [PRODUCT NAME] - Executive Summary
30
+ ```markdown
31
+ # [PRODUCT NAME]
32
+ ## Executive Summary
29
33
 
30
- ### The Opportunity
31
- [2-3 sentences describing the market problem and opportunity size]
34
+ **[One-line tagline describing what the product is]**
35
+
36
+ ---
37
+
38
+ ## At a Glance
39
+
40
+ | | |
41
+ | ----------------- | -------------------------------------- |
42
+ | **Product Type** | [Category/type of product] |
43
+ | **Target Market** | [Primary target market/segment] |
44
+ | **Platform** | [Web/Mobile/Desktop/API/etc.] |
45
+ | **Technology** | [Key technology stack - if applicable] |
46
+ | **Status** | [Current development/market status] |
47
+
48
+ ---
49
+
50
+ ## What is [Product Name]?
51
+
52
+ [2-3 sentences describing what the product does and its core purpose]
53
+
54
+ ### The Problem We Solve
55
+
56
+ | Challenge | Impact |
57
+ | ----------- | ---------------------- |
58
+ | [Problem 1] | [Business/user impact] |
59
+ | [Problem 2] | [Business/user impact] |
60
+ | [Problem 3] | [Business/user impact] |
61
+ | [Problem 4] | [Business/user impact] |
32
62
 
33
63
  ### Our Solution
34
- [2-3 sentences on what the product does and its core value proposition]
35
64
 
36
- ### Target Customer
37
- [Specific customer segment with key characteristics]
65
+ [1-2 sentences describing the solution approach]
66
+
67
+ ```
68
+ [Visual flow diagram using ASCII/text if applicable]
69
+ Example:
70
+ Process A → Process B → Process C
71
+ ↓ ↓ ↓
72
+ Output 1 Output 2 Output 3
73
+ ```
74
+
75
+ ---
76
+
77
+ ## Core Capabilities
78
+
79
+ ### 1️⃣ [Capability Category 1]
80
+ - [Feature/capability bullet point]
81
+ - [Feature/capability bullet point]
82
+ - [Feature/capability bullet point]
83
+
84
+ ### 2️⃣ [Capability Category 2]
85
+ - [Feature/capability bullet point]
86
+ - [Feature/capability bullet point]
87
+ - [Feature/capability bullet point]
88
+
89
+ ### 3️⃣ [Capability Category 3]
90
+ - [Feature/capability bullet point]
91
+ - [Feature/capability bullet point]
92
+ - [Feature/capability bullet point]
38
93
 
39
- ### Key Differentiators
40
- - [Differentiator 1]
41
- - [Differentiator 2]
42
- - [Differentiator 3]
94
+ [Add more categories as needed - typically 3-6]
43
95
 
44
- ### Business Model
45
- [1-2 sentences on how the product generates revenue]
96
+ ---
97
+
98
+ ## Key Benefits
46
99
 
47
- ### Traction & Validation
48
- [Key metrics, milestones, or validation points - use "Target:" prefix for projections]
100
+ | Benefit | Description |
101
+ | ----------------- | ------------------------ |
102
+ | **⏱️ [Benefit 1]** | [Description of benefit] |
103
+ | **✅ [Benefit 2]** | [Description of benefit] |
104
+ | **📊 [Benefit 3]** | [Description of benefit] |
105
+ | **🔐 [Benefit 4]** | [Description of benefit] |
106
+ | **📁 [Benefit 5]** | [Description of benefit] |
107
+ | **🔄 [Benefit 6]** | [Description of benefit] |
49
108
 
50
- ### Competitive Position
51
- [Brief competitive landscape and positioning statement]
109
+ ---
52
110
 
53
- ### Strategic Fit
54
- [How this aligns with broader company/market strategy]
111
+ ## User Roles Supported
55
112
 
56
- ### Ask / Next Steps
57
- [Clear call-to-action or decision needed]
113
+ | Role | Primary Functions |
114
+ | ------------ | ----------------------------------- |
115
+ | **[Role 1]** | [Key responsibilities/capabilities] |
116
+ | **[Role 2]** | [Key responsibilities/capabilities] |
117
+ | **[Role 3]** | [Key responsibilities/capabilities] |
118
+ | **[Role 4]** | [Key responsibilities/capabilities] |
58
119
 
59
120
  ---
60
- **Status:** [Current stage]
61
- **Owner:** [Product lead/team]
62
- **Last Updated:** [Date]
121
+
122
+ ## System Architecture / Modules
123
+
124
+ ```
125
+ ┌─────────────────────────────────────────────────────────┐
126
+ │ [PRODUCT NAME] │
127
+ ├─────────────┬─────────────┬─────────────┬──────────────┤
128
+ │ [Module 1] │ [Module 2] │ [Module 3] │ [Module 4] │
129
+ │ (Function) │ (Function) │ (Function) │ (Function) │
130
+ ├─────────────┼─────────────┼─────────────┼──────────────┤
131
+ │ [Module 5] │ [Module 6] │ [Module 7] │ [Module 8] │
132
+ │ (Function) │ (Function) │ (Function) │ (Function) │
133
+ └─────────────┴─────────────┴─────────────┴──────────────┘
134
+ ```
135
+
136
+ **[X] modules** working together seamlessly.
137
+
138
+ ---
139
+
140
+ ## Infrastructure Highlights
141
+
142
+ - **[Highlight 1]** — [Brief description]
143
+ - **[Highlight 2]** — [Brief description]
144
+ - **[Highlight 3]** — [Brief description]
145
+ - **[Highlight 4]** — [Brief description]
146
+ - **[Highlight 5]** — [Brief description]
147
+
148
+ ---
149
+
150
+ ## [Domain-Specific Features Section]
151
+
152
+ ### [Subsection Title]
153
+ - ✅ [Feature with checkmark]
154
+ - ✅ [Feature with checkmark]
155
+ - ✅ [Feature with checkmark]
156
+
157
+ ### [Workflow/Process Name]
158
+ ```
159
+ [Step 1] → [Step 2] → [Step 3] → [Step 4] → [Step 5]
160
+ ```
161
+
162
+ ### [Additional Subsection if needed]
163
+ - **[State 1]** → **[State 2]** → **[State 3]**
164
+ - [Additional context]
165
+
166
+ ---
167
+
168
+ ## Dashboard / Analytics
169
+
170
+ | Widget | Purpose |
171
+ | ---------- | ------------------------- |
172
+ | [Widget 1] | [What it monitors/tracks] |
173
+ | [Widget 2] | [What it monitors/tracks] |
174
+ | [Widget 3] | [What it monitors/tracks] |
175
+ | [Widget 4] | [What it monitors/tracks] |
176
+ | [Widget 5] | [What it monitors/tracks] |
177
+
178
+ ---
179
+
180
+ ## Competitive Advantages
181
+
182
+ | Feature | [Product Name] | Traditional Methods |
183
+ | ----------- | -------------- | ------------------- |
184
+ | [Feature 1] | ✅ [Advantage] | ❌ [Disadvantage] |
185
+ | [Feature 2] | ✅ [Advantage] | ❌ [Disadvantage] |
186
+ | [Feature 3] | ✅ [Advantage] | ❌ [Disadvantage] |
187
+ | [Feature 4] | ✅ [Advantage] | ❌ [Disadvantage] |
188
+ | [Feature 5] | ✅ [Advantage] | ❌ [Disadvantage] |
189
+
190
+ ---
191
+
192
+ ## Roadmap Considerations
193
+
194
+ ### Current State
195
+ - [Current capability/status point]
196
+ - [Current capability/status point]
197
+ - [Current capability/status point]
198
+
199
+ ### Potential Enhancements
200
+ | Priority | Enhancement |
201
+ | -------- | ------------------------- |
202
+ | High | [Enhancement description] |
203
+ | High | [Enhancement description] |
204
+ | Medium | [Enhancement description] |
205
+ | Medium | [Enhancement description] |
206
+ | Low | [Enhancement description] |
207
+
208
+ ---
209
+
210
+ ## Technical Foundation
211
+
212
+ | Component | Choice | Why |
213
+ | ----------- | ------------------- | ----------- |
214
+ | [Component] | [Technology choice] | [Rationale] |
215
+ | [Component] | [Technology choice] | [Rationale] |
216
+ | [Component] | [Technology choice] | [Rationale] |
217
+ | [Component] | [Technology choice] | [Rationale] |
218
+ | [Component] | [Technology choice] | [Rationale] |
219
+
220
+ ---
221
+
222
+ ## Getting Started
223
+
224
+ ### For New Implementations
225
+ 1. [Step 1]
226
+ 2. [Step 2]
227
+ 3. [Step 3]
228
+ 4. [Step 4]
229
+ 5. [Step 5]
230
+ 6. [Step 6]
231
+
232
+ ### For Existing Users
233
+ - [Migration/upgrade consideration]
234
+ - [Data preservation note]
235
+ - [Compliance/audit note]
236
+
237
+ ---
238
+
239
+ ## Summary
240
+
241
+ **[Product Name]** transforms [domain/industry] operations by:
242
+
243
+ 1. **[Verb-ing]** [benefit/outcome]
244
+ 2. **[Verb-ing]** [benefit/outcome]
245
+ 3. **[Verb-ing]** [benefit/outcome]
246
+ 4. **[Verb-ing]** [benefit/outcome]
247
+ 5. **[Verb-ing]** [benefit/outcome]
248
+
249
+ ---
250
+
251
+ ## Document Information
252
+
253
+ | | |
254
+ | ---------------------- | ------------------------------ |
255
+ | **Version** | [Version number] |
256
+ | **Date** | [Current date] |
257
+ | **Classification** | Internal - Executive Summary |
258
+ | **Full Specification** | See `product-specification.md` |
259
+
260
+ ---
261
+
262
+ *For technical details, data models, and implementation specifications, refer to the complete Product Specification Document.*
263
+ ```
63
264
 
64
265
  # Writing Standards
65
266
  - **Tone:** Confident, data-informed, strategic
66
- - **Length:** 1 page maximum (300-500 words)
267
+ - **Length:** Comprehensive but scannable (typically 200-400 lines)
67
268
  - **Language:** Executive-friendly, minimal jargon
68
- - **Numbers:** Include quantified metrics wherever possible
69
- - **Clarity:** Each section should be understandable in isolation
269
+ - **Visuals:** Use tables for structured data, ASCII diagrams for flows/architecture
270
+ - **Icons:** Use emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄, 1️⃣, 2️⃣, etc.) to improve scannability
271
+ - **Checkmarks:** Use ✅ for features/advantages, ❌ for competitor disadvantages
70
272
 
71
273
  # Quality Criteria
72
- 1. A busy executive can understand the product in under 2 minutes
73
- 2. The value proposition is immediately clear
74
- 3. Key decisions or asks are explicit
75
- 4. Claims are specific and quantified where possible
76
- 5. Strategic rationale is evident
274
+ 1. A busy executive can understand the product in under 5 minutes
275
+ 2. The value proposition is immediately clear from the first sections
276
+ 3. Tables make data comparison easy and quick to scan
277
+ 4. Visual diagrams help explain system architecture and workflows
278
+ 5. Competitive positioning is explicit and easy to understand
279
+ 6. Technical and non-technical stakeholders can both extract value
77
280
 
78
281
  # Special Instructions
79
- - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION]
282
+ - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION] or use placeholder text like [TBD]
80
283
  - Prioritize clarity over comprehensiveness
81
284
  - Lead with impact, not features
82
285
  - Use active voice and strong verbs
83
286
  - Avoid superlatives without supporting data
84
- - If competitive information is sparse, focus on unique value rather than comparisons
287
+ - If competitive information is sparse, focus on unique value rather than comparisons
288
+ - Adapt section headers to match the product domain (e.g., "Financial Features" for fintech, "Clinical Workflow" for healthcare)
289
+ - Skip sections that don't apply to the product type (e.g., "Technical Foundation" for non-software products)
package/src/cli/index.ts CHANGED
@@ -9,7 +9,7 @@ const program = new Command();
9
9
  program
10
10
  .name('prompter')
11
11
  .description('Enhance prompts directly in your AI coding workflow')
12
- .version('0.4.0');
12
+ .version('0.4.1');
13
13
 
14
14
  program
15
15
  .command('init')
package/src/core/templates/slash-command-templates.ts CHANGED
@@ -709,7 +709,7 @@ const productBriefWorkflow = `# Role & Expertise
709
709
  You are a Senior Product Manager with 15+ years of experience crafting executive-level product briefs for Fortune 500 companies. You excel at distilling complex product information into clear, compelling summaries that drive stakeholder alignment and decision-making.
710
710
 
711
711
  # Context
712
- You are creating a Product Brief (Executive Summary) - a concise, high-impact document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders who need to quickly understand the product's value proposition, market opportunity, and strategic fit.
712
+ You are creating a Product Brief (Executive Summary) - a comprehensive, visually-rich document that communicates the essential elements of a product to executives, investors, and cross-functional stakeholders. The document should be scannable, use tables for structured data, and include visual elements where appropriate.
713
713
 
714
714
  # Primary Objective
715
715
  Generate a polished, professional Product Brief that captures the essence of the product in a format suitable for executive review, board presentations, or investor communications.
@@ -725,79 +725,122 @@ Provide any combination of the following:
725
725
  - Current status/stage
726
726
  - Key metrics or traction (if available)
727
727
  - Strategic goals
728
+ - Technical stack (if applicable)
729
+ - User roles
728
730
 
729
731
  *Note: Work with whatever information is provided; make reasonable inferences for gaps while flagging assumptions.*
730
732
 
731
733
  # Output Format
732
734
 
733
- ## [PRODUCT NAME] - Executive Summary
735
+ The output should follow this comprehensive structure:
734
736
 
735
- ### The Opportunity
736
- [2-3 sentences describing the market problem and opportunity size]
737
+ ## 1. Header Section
738
+ \`\`\`markdown
739
+ # [PRODUCT NAME]
740
+ ## Executive Summary
737
741
 
738
- ### Our Solution
739
- [2-3 sentences on what the product does and its core value proposition]
742
+ **[One-line tagline describing what the product is]**
740
743
 
741
- ### Target Customer
742
- [Specific customer segment with key characteristics]
744
+ ---
743
745
 
744
- ### Key Differentiators
745
- - [Differentiator 1]
746
- - [Differentiator 2]
747
- - [Differentiator 3]
746
+ ## At a Glance
748
747
 
749
- ### Business Model
750
- [1-2 sentences on how the product generates revenue]
748
+ | | |
749
+ | ----------------- | ---------------------------------------- |
750
+ | **Product Type** | [Category/type of product] |
751
+ | **Target Market** | [Primary target market/segment] |
752
+ | **Platform** | [Web/Mobile/Desktop/API/etc.] |
753
+ | **Technology** | [Key technology stack - if applicable] |
754
+ | **Status** | [Current development/market status] |
755
+ \`\`\`
751
756
 
752
- ### Traction & Validation
753
- [Key metrics, milestones, or validation points - use "Target:" prefix for projections]
757
+ ## 2. Product Overview
758
+ - "What is [Product Name]?" section with 2-3 sentences
759
+ - "The Problem We Solve" table (Challenge | Impact)
760
+ - "Our Solution" with ASCII flow diagram
754
761
 
755
- ### Competitive Position
756
- [Brief competitive landscape and positioning statement]
762
+ ## 3. Core Capabilities
763
+ - Numbered sections (1️⃣, 2️⃣, 3️⃣, etc.) with bullet points
764
+ - Typically 3-6 capability categories
757
765
 
758
- ### Strategic Fit
759
- [How this aligns with broader company/market strategy]
766
+ ## 4. Key Benefits
767
+ - Table format with emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄)
768
+ - Benefit name | Description
760
769
 
761
- ### Ask / Next Steps
762
- [Clear call-to-action or decision needed]
770
+ ## 5. User Roles Supported
771
+ - Table: Role | Primary Functions
763
772
 
764
- ---
765
- **Status:** [Current stage]
766
- **Owner:** [Product lead/team]
767
- **Last Updated:** [Date]
773
+ ## 6. System Architecture / Modules
774
+ - ASCII box diagram showing module structure
775
+ - Summary of module count
776
+
777
+ ## 7. Infrastructure Highlights
778
+ - Bullet points with bold headers
779
+
780
+ ## 8. Domain-Specific Features
781
+ - Subsections with checkmarks (✅)
782
+ - Workflow diagrams using arrows (→)
783
+
784
+ ## 9. Dashboard / Analytics
785
+ - Table: Widget | Purpose
786
+
787
+ ## 10. Competitive Advantages
788
+ - Comparison table: Feature | [Product] | Traditional Methods
789
+ - Use ✅ for advantages, ❌ for competitor disadvantages
790
+
791
+ ## 11. Roadmap Considerations
792
+ - Current State (bullet points)
793
+ - Potential Enhancements table (Priority | Enhancement)
794
+
795
+ ## 12. Technical Foundation
796
+ - Table: Component | Choice | Why
797
+
798
+ ## 13. Getting Started
799
+ - For New Implementations (numbered steps)
800
+ - For Existing Users (bullet points)
801
+
802
+ ## 14. Summary
803
+ - "[Product Name] transforms [domain] by:" followed by numbered benefits
804
+
805
+ ## 15. Document Information
806
+ - Table with Version, Date, Classification, Full Specification reference
768
807
 
769
808
  # Writing Standards
770
809
  - **Tone:** Confident, data-informed, strategic
771
- - **Length:** 1 page maximum (300-500 words)
810
+ - **Length:** Comprehensive but scannable (typically 200-400 lines)
772
811
  - **Language:** Executive-friendly, minimal jargon
773
- - **Numbers:** Include quantified metrics wherever possible
774
- - **Clarity:** Each section should be understandable in isolation
812
+ - **Visuals:** Use tables for structured data, ASCII diagrams for flows/architecture
813
+ - **Icons:** Use emoji icons (⏱️, ✅, 📊, 🔐, 📁, 🔄, 1️⃣, 2️⃣, etc.) to improve scannability
814
+ - **Checkmarks:** Use ✅ for features/advantages, ❌ for competitor disadvantages
775
815
 
776
816
  # Quality Criteria
777
- 1. A busy executive can understand the product in under 2 minutes
778
- 2. The value proposition is immediately clear
779
- 3. Key decisions or asks are explicit
780
- 4. Claims are specific and quantified where possible
781
- 5. Strategic rationale is evident
817
+ 1. A busy executive can understand the product in under 5 minutes
818
+ 2. The value proposition is immediately clear from the first sections
819
+ 3. Tables make data comparison easy and quick to scan
820
+ 4. Visual diagrams help explain system architecture and workflows
821
+ 5. Competitive positioning is explicit and easy to understand
822
+ 6. Technical and non-technical stakeholders can both extract value
782
823
 
783
824
  # Special Instructions
784
- - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION]
825
+ - If information is incomplete, make reasonable assumptions and mark with [ASSUMPTION] or use placeholder text like [TBD]
785
826
  - Prioritize clarity over comprehensiveness
786
827
  - Lead with impact, not features
787
828
  - Use active voice and strong verbs
788
829
  - Avoid superlatives without supporting data
789
830
  - If competitive information is sparse, focus on unique value rather than comparisons
831
+ - Adapt section headers to match the product domain (e.g., "Financial Features" for fintech, "Clinical Workflow" for healthcare)
832
+ - Skip sections that don't apply to the product type (e.g., "Technical Foundation" for non-software products)
790
833
 
791
834
  ## WORKFLOW STEPS
792
835
  1. Read the user's input about the product
793
836
  2. Generate a unique, URL-friendly slug from the product name (lowercase, hyphen-separated)
794
- 3. Create the directory \`prompter/<slug>/\` if it doesn't exist
837
+ 3. Create the directory \\\`prompter/<slug>/\\\` if it doesn't exist
795
838
  4. Generate the complete Product Brief following all requirements above
796
- 5. Save the Product Brief to \`prompter/<slug>/product-brief.md\`
839
+ 5. Save the Product Brief to \\\`prompter/<slug>/product-brief.md\\\`
797
840
  6. Report the saved file path
798
841
 
799
842
  ## REFERENCE
800
- - Read \`prompter/project.md\` for project context if needed`;
843
+ - Read \\\`prompter/project.md\\\` for project context if needed`;
801
844
 
802
845
  export const slashCommandBodies: Record<SlashCommandId, string> = {
803
846
  enhance: enhanceWorkflow,