gspec 1.18.0 → 1.19.0

package/dist/opencode/{gspec-profile → skills/gspec-profile}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-profile
-description: Generate or update the product profile (gspec/profile.md) — what the product is, who it serves, and why it exists. TRIGGER when the user wants to define, describe, capture, or refine product identity, target users, audience, vision, positioning, or value proposition — e.g. "define my product", "who are the users", "describe what I'm building", "what is this app", "capture the vision", "write a profile". Prefer this skill over drafting a profile ad hoc.
+name: "gspec-profile"
+description: "Generate or update gspec/profile.md — what the product is, who it serves, and why. TRIGGER when the user wants to define or refine product identity, users, audience, vision, or value proposition — e.g. \"define my product\", \"what is this app\"."
 ---
 
 You are a Product Strategist.
@@ -36,7 +36,6 @@ You should:
   - The product type is ambiguous
   - The target audience or user is unclear
   - The core value proposition is ambiguous
-  - *(Commercial products only)* The business model or monetization strategy is unspecified
   - *(Commercial products only)* Competitive positioning is unknown
 - **When asking questions**, offer 2-3 specific suggestions to guide the discussion
 - Write for the audience the product actually has (internal stakeholders, end users, contributors, the public, etc.)
@@ -44,6 +43,7 @@ You should:
 - Focus on the "what" and "why", not the "how"
 - Use clear, jargon-free language where possible
 - **Mark sections as "Not Applicable"** when they don't apply to this product, and briefly note why (e.g., "Not applicable — internal tool, no external market"). Do not fabricate content to fill a section.
+- **Do not include business model, pricing, or success metrics sections** unless the user explicitly asks for them — those are go-to-market concerns, not product identity.
 
 ---
 
@@ -129,23 +129,7 @@ You should:
 - Indirect competitors, alternatives, or incumbent approaches
 - White space or gaps this product fills
 
-### 8. Business Model
-
-*Skip or mark "Not Applicable" for non-commercial products (internal tools, open source, personal projects, research). For OSS, consider replacing this section with a "Sustainability & Governance" note covering funding, maintainership, and contribution model if relevant.*
-
-#### Revenue Model
-- How the product makes money (subscription, transaction fees, freemium, ads, etc.)
-- Pricing strategy (high-level)
-
-#### Customer Acquisition
-- How customers discover and adopt the product
-- Key channels
-
-#### Growth Strategy
-- How the product plans to scale
-- Expansion opportunities
-
-### 9. Brand & Positioning
+### 8. Brand & Positioning
 
 *Skip or simplify for internal tools and products with no external-facing presence. Most products still benefit from a positioning statement even if they skip brand personality and messaging.*
 
@@ -160,24 +144,7 @@ You should:
 - Core messages to communicate consistently
 - Elevator pitch
 
-### 10. Success Metrics
-
-*Adapt to the product type. Always include user/adoption metrics if meaningful. Include business metrics only for commercial products.*
-
-#### Adoption & Engagement Metrics
-- Adoption or usage rates (installs, active users, repo stars, internal rollout percentage, etc.)
-- Engagement metrics appropriate to the product
-- User satisfaction (NPS, CSAT, contributor sentiment, internal feedback, etc.)
-
-#### Business Metrics *(commercial products only)*
-- Revenue targets
-- Paid user growth goals
-- Market share objectives
-
-#### Project Health Metrics *(optional, especially for OSS / internal tools)*
-- Contributor count, issue response time, release cadence, uptime, etc.
-
-### 11. Public-Facing Information (Optional)
+### 9. Public-Facing Information (Optional)
 
 *Skip entirely for internal tools, private projects, or anything without a public presence.*
 
@@ -196,21 +163,7 @@ You should:
 - Media kit essentials
 - Key talking points
 
-### 12. Product Roadmap Vision
-
-#### Current Focus
-- What's being built now
-- Immediate priorities
-
-#### Near-Term (Next)
-- Planned enhancements
-- Next major milestones
-
-#### Long-Term Vision (Later)
-- Future capabilities
-- Strategic direction
-
-### 13. Risks & Assumptions
+### 10. Risks & Assumptions
 
 #### Key Assumptions
 - What we believe to be true

package/dist/opencode/{gspec-research → skills/gspec-research}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-research
-description: Research competitors named in gspec/profile.md and produce a competitive analysis with feature gap identification. TRIGGER when the user wants market research, competitive analysis, competitor teardown, or feature parity comparison — e.g. "research competitors", "competitive analysis", "what are rivals doing", "find feature gaps", "compare to market", "what are we missing vs competitors".
+name: "gspec-research"
+description: "Research competitors from gspec/profile.md and produce a competitive analysis with feature gap identification. TRIGGER when the user wants market research, competitor teardown, or feature parity — e.g. \"research competitors\", \"find feature gaps\"."
 ---
 
 You are a Senior Product Strategist and Competitive Intelligence Analyst at a high-performing software company.

package/dist/opencode/{gspec-stack → skills/gspec-stack}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-stack
-description: Define or update the technology stack (gspec/stack.md) — frameworks, libraries, databases, hosting, CI/CD, and infrastructure. TRIGGER when the user wants to pick, define, revise, or document technology choices — e.g. "what stack should I use", "pick a framework", "define the stack", "choose a database", "set up the tech choices", "what should I build this with". Prefer this skill over suggesting ad-hoc tech picks.
+name: "gspec-stack"
+description: "Define or update gspec/stack.md — frameworks, libraries, databases, hosting, CI/CD, and infrastructure. TRIGGER when the user wants to pick, define, or revise technology choices — e.g. \"what stack should I use\", \"pick a framework\"."
 ---
 
 You are a Senior Software Architect at a high-performing software company.

package/dist/opencode/{gspec-style → skills/gspec-style}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-style
-description: Generate or update the visual style guide — either a renderable HTML design system (gspec/style.html) or a Markdown style guide (gspec/style.md) — defining design tokens, color palette, typography, spacing, and component visual patterns. Also aware of gspec/design/ for external mockups. TRIGGER when the user wants to define or revise the design system, visual language, theme, brand look, or UI aesthetic — e.g. "set up a design system", "pick brand colors", "define the style", "dark mode tokens", "what should this look like", "visual guidelines", "render the style guide". Prefer this skill over producing style docs ad hoc.
+name: "gspec-style"
+description: "Generate or update the visual style guide (gspec/style.html or gspec/style.md) — tokens, palette, typography, spacing, components. TRIGGER when the user wants to define or revise the design system, theme, or look — e.g. \"pick brand colors\"."
 ---
 
 You are a senior UI/UX Designer and Design Systems Architect at a high-performing software company.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "gspec",
-    "version": "1.18.0",
+    "version": "1.19.0",
     "description": "Install gspec specification commands for Claude Code, Cursor, and other AI tools",
     "main": "bin/gspec.js",
     "type": "module",