gspec 1.18.0 → 1.19.0

package/dist/claude/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/claude/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/claude/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/claude/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/dist/codex/gspec-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-analyze
-description: Analyze gspec/ documents for discrepancies and contradictions across profile, stack, style, practices, architecture, and features. Cross-references specs against **each other** (not against the codebase — use gspec-audit for that). Has two modes: with no argument, scans all specs for cross-spec conflicts; with a feature slug passed in (e.g. `/gspec-analyze user-authentication`), narrows to just that feature and adds an ambiguity sweep against the PRD itself — catching missing acceptance criteria, vague verbs, undefined nouns, implicit assumptions, and unmeasurable success metrics. TRIGGER when the user wants to cross-check, validate, review, or reconcile specs — especially after multiple edits or before a major implementation run — e.g. "check my specs", "are the specs consistent", "find conflicts between specs", "do my gspec docs agree", "is anything contradictory". ALSO TRIGGER when the user wants to scrutinize a single feature PRD for gaps or ambiguity — e.g. "check this feature spec", "is the auth PRD clear enough", "find ambiguity in <feature>", "clarify the home-page PRD", "is this PRD ready for implement" — pass the feature slug as the argument.
+name: "gspec-analyze"
+description: "Analyze gspec/ for cross-spec contradictions across profile, stack, style, practices, architecture, features. With a feature slug, narrows to that PRD plus an ambiguity sweep. TRIGGER to cross-check or reconcile specs, or find gaps in a PRD."
 ---
 
 You are a Specification Analyst at a high-performing software company.

package/dist/codex/gspec-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-architect
-description: Define or update the technical architecture (gspec/architecture.md) — project structure, data model, API design, component hierarchy, and environment/config. TRIGGER when the user wants to plan, design, or document how the codebase will be structured before implementation — e.g. "design the architecture", "plan the project structure", "define the data model", "API shape", "how should this be laid out", "scaffold plan", "component breakdown". Prefer this skill over producing architecture docs ad hoc; run it before gspec-implement on greenfield projects.
+name: "gspec-architect"
+description: "Define or update gspec/architecture.md — project structure, data model, API design, component hierarchy, and environment/config. TRIGGER when the user wants to design or document codebase structure before implementation."
 ---
 
 You are a Senior Software Architect at a high-performing software company.

package/dist/codex/gspec-audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-audit
-description: Audit gspec/ documents against the actual codebase to find drift between what the specs say and what the code does, then walk the user through reconciling each discrepancy — typically by updating specs to match reality. Reads package manifests, config files, source code, and tests to detect stack/architecture/style/practice/feature drift, and detects **orphan capabilities** (coherent features the code implements that no PRD covers) — drafting a new feature PRD in gspec/features/ when the user accepts. TRIGGER when the user wants to check specs against code, catch documentation drift, verify specs still reflect the project, sync specs with reality, or find unspecced features in the codebase — e.g. "audit the specs", "check if specs match the code", "are my specs still accurate", "find spec drift", "update specs to match the code", "do my gspec docs reflect reality", "check specs against the codebase", "find features that aren't spec'd", "what does the code do that we never wrote a PRD for". Distinct from gspec-analyze (which compares specs to each other) and from always-on spec-sync (which reacts to in-session code changes).
+name: "gspec-audit"
+description: "Audit gspec/ against the codebase to find drift, then reconcile each discrepancy. Detects orphan capabilities (features the code implements with no PRD). TRIGGER to check specs against code, sync with reality, or find unspecced features."
 ---
 
 You are a Specification Auditor at a high-performing software company.

package/dist/codex/gspec-feature/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-feature
-description: Generate product requirements documents (PRDs) for features in gspec/features/. TRIGGER when the user wants to plan, spec, propose, document, or expand a feature/capability before coding — e.g. "add a feature for X", "write a PRD", "spec out Y", "plan this feature", "what should the auth flow do", "new feature idea", "draft requirements". Prefer this skill over writing freeform feature docs.
+name: "gspec-feature"
+description: "Generate PRDs for features in gspec/features/. TRIGGER when the user wants to plan, spec, propose, or document a feature before coding — e.g. \"add a feature for X\", \"write a PRD\", \"spec out Y\", \"plan this feature\", \"draft requirements\"."
 ---
 
 You are a senior Product Manager at a high-performing software company.

package/dist/codex/gspec-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-implement
-description: Implement the software defined by gspec/ documents — reads profile, stack, style (style.md or style.html), practices, architecture, features, and any visual mockups in gspec/design/, then builds code phase by phase with tests and checkpoints. **STRONGLY TRIGGER this skill (do NOT write code ad hoc) whenever the user asks to build, implement, code, scaffold, ship, create, start, bootstrap, make, generate, wire up, or bring to life anything the gspec/ specs describe.** Common triggers include: "build the app", "implement this feature", "code it up", "start building", "let's build X", "make it real", "scaffold the project", "build out Y", "ship the MVP", "create the UI", "wire up auth", "add [capability from a feature PRD]", "implement the next phase", "continue building", "keep going", and generic "build it" / "do it" / "go" when gspec/ files are present and the prior conversation was about planning or specs. Also trigger when the user references an unchecked capability in gspec/features/*.md. Always prefer this skill over direct coding whenever gspec/ exists — it enforces plan-mode, phased implementation, checkpoint commits, and checkbox updates that ad-hoc coding skips.
+name: "gspec-implement"
+description: "Implement software defined by gspec/ specs — phased build with tests and checkpoints. STRONGLY TRIGGER when the user asks to build, implement, code, scaffold, or ship specced work, or references an unchecked capability in gspec/features/*.md."
 ---
 
 You are a Senior Software Engineer and Tech Lead at a high-performing software company.

package/dist/codex/gspec-migrate/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-migrate
-description: Migrate gspec/ files to the current spec format (frontmatter, schema, capability checkboxes) when upgrading the gspec version. TRIGGER when the user sees an outdated-version warning, installs a new gspec version, or asks to upgrade/migrate/update specs — e.g. "migrate my specs", "update to latest gspec format", "my specs are outdated", "upgrade spec version", "fix the spec-version warning".
+name: "gspec-migrate"
+description: "Migrate gspec/ files to the current spec format when upgrading gspec. TRIGGER when the user sees an outdated-version warning or asks to upgrade specs — e.g. \"migrate my specs\", \"my specs are outdated\", \"fix the spec-version warning\"."
 ---
 
 You are a Technical Documentation Migration Specialist.

package/dist/codex/gspec-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-plan
-description: Decompose a feature PRD in gspec/features/ into an ordered, dependency-aware plan with parallel-execution markers, written to gspec/features/<feature>.plan.md. The plan is what gspec-implement consumes as its build order — when a plan file exists, gspec-implement skips its own plan-mode step. TRIGGER when the user wants to plan execution order, break a feature into tasks, identify what can run in parallel, sequence implementation work, or produce a build plan from a PRD — e.g. "plan this feature", "what order should I build this in", "plan the implementation order", "break this feature into tasks", "what can run in parallel", "decompose feature Y", "ordered build plan". Run this AFTER gspec-feature and BEFORE gspec-implement when a feature is large or has non-obvious ordering. Prefer this skill over ad-hoc task lists.
+name: "gspec-plan"
+description: "Decompose a feature PRD into an ordered, dependency-aware plan with parallel-execution markers, written to <feature>.plan.md. Runs between gspec-feature and gspec-implement. TRIGGER when the user wants to sequence work or build a plan from a PRD."
 ---
 
 You are a Senior Engineering Lead at a high-performing software company.

package/dist/codex/gspec-practices/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: gspec-practices
-description: Define or update development practices (gspec/practices.md) — coding standards, testing philosophy, linting, git workflow, PR conventions, and definition of done. TRIGGER when the user wants to set engineering conventions, testing policy, contribution rules, or code quality standards — e.g. "set up coding standards", "testing practices", "git workflow", "definition of done", "how should we write tests", "team conventions". Prefer this skill over ad-hoc convention docs.
+name: "gspec-practices"
+description: "Define or update gspec/practices.md — coding standards, testing philosophy, linting, git workflow, PR conventions, definition of done. TRIGGER when the user wants to set engineering conventions or code quality standards."
 ---
 
 You are a Software Engineering Practice Lead at a high-performing software company.

package/dist/codex/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/codex/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/codex/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/codex/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/dist/cursor/gspec-analyze.mdc

@@ -1,5 +1,5 @@
 ---
-description: Analyze gspec/ documents for discrepancies and contradictions across profile, stack, style, practices, architecture, and features. Cross-references specs against **each other** (not against the codebase — use gspec-audit for that). Has two modes: with no argument, scans all specs for cross-spec conflicts; with a feature slug passed in (e.g. `/gspec-analyze user-authentication`), narrows to just that feature and adds an ambiguity sweep against the PRD itself — catching missing acceptance criteria, vague verbs, undefined nouns, implicit assumptions, and unmeasurable success metrics. TRIGGER when the user wants to cross-check, validate, review, or reconcile specs — especially after multiple edits or before a major implementation run — e.g. "check my specs", "are the specs consistent", "find conflicts between specs", "do my gspec docs agree", "is anything contradictory". ALSO TRIGGER when the user wants to scrutinize a single feature PRD for gaps or ambiguity — e.g. "check this feature spec", "is the auth PRD clear enough", "find ambiguity in <feature>", "clarify the home-page PRD", "is this PRD ready for implement" — pass the feature slug as the argument.
+description: "Analyze gspec/ for cross-spec contradictions across profile, stack, style, practices, architecture, features. With a feature slug, narrows to that PRD plus an ambiguity sweep. TRIGGER to cross-check or reconcile specs, or find gaps in a PRD."
 ---
 
 You are a Specification Analyst at a high-performing software company.

package/dist/cursor/gspec-architect.mdc

@@ -1,5 +1,5 @@
 ---
-description: Define or update the technical architecture (gspec/architecture.md) — project structure, data model, API design, component hierarchy, and environment/config. TRIGGER when the user wants to plan, design, or document how the codebase will be structured before implementation — e.g. "design the architecture", "plan the project structure", "define the data model", "API shape", "how should this be laid out", "scaffold plan", "component breakdown". Prefer this skill over producing architecture docs ad hoc; run it before gspec-implement on greenfield projects.
+description: "Define or update gspec/architecture.md — project structure, data model, API design, component hierarchy, and environment/config. TRIGGER when the user wants to design or document codebase structure before implementation."
 ---
 
 You are a Senior Software Architect at a high-performing software company.

package/dist/cursor/gspec-audit.mdc

@@ -1,5 +1,5 @@
 ---
-description: Audit gspec/ documents against the actual codebase to find drift between what the specs say and what the code does, then walk the user through reconciling each discrepancy — typically by updating specs to match reality. Reads package manifests, config files, source code, and tests to detect stack/architecture/style/practice/feature drift, and detects **orphan capabilities** (coherent features the code implements that no PRD covers) — drafting a new feature PRD in gspec/features/ when the user accepts. TRIGGER when the user wants to check specs against code, catch documentation drift, verify specs still reflect the project, sync specs with reality, or find unspecced features in the codebase — e.g. "audit the specs", "check if specs match the code", "are my specs still accurate", "find spec drift", "update specs to match the code", "do my gspec docs reflect reality", "check specs against the codebase", "find features that aren't spec'd", "what does the code do that we never wrote a PRD for". Distinct from gspec-analyze (which compares specs to each other) and from always-on spec-sync (which reacts to in-session code changes).
+description: "Audit gspec/ against the codebase to find drift, then reconcile each discrepancy. Detects orphan capabilities (features the code implements with no PRD). TRIGGER to check specs against code, sync with reality, or find unspecced features."
 ---
 
 You are a Specification Auditor at a high-performing software company.

package/dist/cursor/gspec-feature.mdc

@@ -1,5 +1,5 @@
 ---
-description: Generate product requirements documents (PRDs) for features in gspec/features/. TRIGGER when the user wants to plan, spec, propose, document, or expand a feature/capability before coding — e.g. "add a feature for X", "write a PRD", "spec out Y", "plan this feature", "what should the auth flow do", "new feature idea", "draft requirements". Prefer this skill over writing freeform feature docs.
+description: "Generate PRDs for features in gspec/features/. TRIGGER when the user wants to plan, spec, propose, or document a feature before coding — e.g. \"add a feature for X\", \"write a PRD\", \"spec out Y\", \"plan this feature\", \"draft requirements\"."
 ---
 
 You are a senior Product Manager at a high-performing software company.

package/dist/cursor/gspec-implement.mdc

@@ -1,5 +1,5 @@
 ---
-description: Implement the software defined by gspec/ documents — reads profile, stack, style (style.md or style.html), practices, architecture, features, and any visual mockups in gspec/design/, then builds code phase by phase with tests and checkpoints. **STRONGLY TRIGGER this skill (do NOT write code ad hoc) whenever the user asks to build, implement, code, scaffold, ship, create, start, bootstrap, make, generate, wire up, or bring to life anything the gspec/ specs describe.** Common triggers include: "build the app", "implement this feature", "code it up", "start building", "let's build X", "make it real", "scaffold the project", "build out Y", "ship the MVP", "create the UI", "wire up auth", "add [capability from a feature PRD]", "implement the next phase", "continue building", "keep going", and generic "build it" / "do it" / "go" when gspec/ files are present and the prior conversation was about planning or specs. Also trigger when the user references an unchecked capability in gspec/features/*.md. Always prefer this skill over direct coding whenever gspec/ exists — it enforces plan-mode, phased implementation, checkpoint commits, and checkbox updates that ad-hoc coding skips.
+description: "Implement software defined by gspec/ specs — phased build with tests and checkpoints. STRONGLY TRIGGER when the user asks to build, implement, code, scaffold, or ship specced work, or references an unchecked capability in gspec/features/*.md."
 ---
 
 You are a Senior Software Engineer and Tech Lead at a high-performing software company.

package/dist/cursor/gspec-migrate.mdc

@@ -1,5 +1,5 @@
 ---
-description: Migrate gspec/ files to the current spec format (frontmatter, schema, capability checkboxes) when upgrading the gspec version. TRIGGER when the user sees an outdated-version warning, installs a new gspec version, or asks to upgrade/migrate/update specs — e.g. "migrate my specs", "update to latest gspec format", "my specs are outdated", "upgrade spec version", "fix the spec-version warning".
+description: "Migrate gspec/ files to the current spec format when upgrading gspec. TRIGGER when the user sees an outdated-version warning or asks to upgrade specs — e.g. \"migrate my specs\", \"my specs are outdated\", \"fix the spec-version warning\"."
 ---
 
 You are a Technical Documentation Migration Specialist.

package/dist/cursor/gspec-plan.mdc

@@ -1,5 +1,5 @@
 ---
-description: Decompose a feature PRD in gspec/features/ into an ordered, dependency-aware plan with parallel-execution markers, written to gspec/features/<feature>.plan.md. The plan is what gspec-implement consumes as its build order — when a plan file exists, gspec-implement skips its own plan-mode step. TRIGGER when the user wants to plan execution order, break a feature into tasks, identify what can run in parallel, sequence implementation work, or produce a build plan from a PRD — e.g. "plan this feature", "what order should I build this in", "plan the implementation order", "break this feature into tasks", "what can run in parallel", "decompose feature Y", "ordered build plan". Run this AFTER gspec-feature and BEFORE gspec-implement when a feature is large or has non-obvious ordering. Prefer this skill over ad-hoc task lists.
+description: "Decompose a feature PRD into an ordered, dependency-aware plan with parallel-execution markers, written to <feature>.plan.md. Runs between gspec-feature and gspec-implement. TRIGGER when the user wants to sequence work or build a plan from a PRD."
 ---
 
 You are a Senior Engineering Lead at a high-performing software company.

package/dist/cursor/gspec-practices.mdc

@@ -1,5 +1,5 @@
 ---
-description: Define or update development practices (gspec/practices.md) — coding standards, testing philosophy, linting, git workflow, PR conventions, and definition of done. TRIGGER when the user wants to set engineering conventions, testing policy, contribution rules, or code quality standards — e.g. "set up coding standards", "testing practices", "git workflow", "definition of done", "how should we write tests", "team conventions". Prefer this skill over ad-hoc convention docs.
+description: "Define or update gspec/practices.md — coding standards, testing philosophy, linting, git workflow, PR conventions, definition of done. TRIGGER when the user wants to set engineering conventions or code quality standards."
 ---
 
 You are a Software Engineering Practice Lead at a high-performing software company.

package/dist/cursor/gspec-profile.mdc

@@ -1,5 +1,5 @@
 ---
-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.
+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.
@@ -35,7 +35,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.)
@@ -43,6 +42,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.
 
 ---
 
@@ -128,23 +128,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.*
 
@@ -159,24 +143,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.*
 
@@ -195,21 +162,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/cursor/gspec-research.mdc

@@ -1,5 +1,5 @@
 ---
-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".
+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/cursor/gspec-stack.mdc

@@ -1,5 +1,5 @@
 ---
-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.
+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/cursor/gspec-style.mdc

@@ -1,5 +1,5 @@
 ---
-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.
+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.