gspec 1.6.0 → 1.10.0

package/commands/gspec.practices.md

@@ -34,8 +34,10 @@ You should:
 - Focus on practices that matter for this specific project
 - Avoid generic advice that doesn't apply
 - **Do NOT include technology stack information** — this is documented separately
-- **Do NOT prescribe specific testing frameworks, tools, or libraries** — focus on testing principles, patterns, and practices, not which tools to use
+- **Do NOT prescribe specific testing frameworks, tools, or libraries** — focus on testing principles, patterns, and practices. The stack document (`gspec/stack.md`) is the single authority for which test tools are used.
+- **DO define CI/CD pipeline structure** — the practices document defines pipeline stages, gates, and ordering (lint → typecheck → test → build → deploy). The stack document defines which CI/CD platform technology is used (GitHub Actions, GitLab CI, etc.).
 - **Mark sections as "Not Applicable"** when they don't apply to this project
+- **Precedence rule**: Where this document conflicts with technology-specific practices in `gspec/stack.md`, the stack's technology-specific practices take precedence for framework-specific concerns (e.g., file naming conventions dictated by a framework). This document governs general engineering principles.
 
 ---
 

package/commands/gspec.research.md

@@ -27,7 +27,7 @@ Before conducting any research, read available gspec documents for context:
    - **Market & Competition** section — direct competitors, indirect competitors or alternatives, white space or gaps the product fills
    - **Value Proposition** section — differentiation and competitive advantages
 2. `gspec/features/*.md` — **Optional.** If feature PRDs exist, read them to understand what capabilities are already specified. This enables gap analysis in later phases.
-3. `gspec/epics/*.md` — **Optional.** If epics exist, read them for broader product scope context.
+
 
 **If `gspec/profile.md` does not exist or has no Market & Competition section**, inform the user that a product profile with competitor information is required for competitive research. Suggest running `gspec-profile` first. Do not proceed without competitor information.
 

package/commands/gspec.stack.md

@@ -91,6 +91,8 @@ You should:
 - Responsive design tooling
 
 - **Note**: Visual design values (colors, typography, spacing) are documented separately as framework-agnostic design tokens; include here how the chosen CSS framework maps to those tokens
+- **Component library** (if applicable) — e.g., shadcn/ui, Headless UI, Radix UI. Component libraries are framework-specific technology choices and belong in the stack, not the style guide.
+- **Note**: Icon libraries (e.g., HeroIcons, Lucide) are defined in `gspec/style.md`, not here. The stack defines the CSS framework and component library; the style defines the icon set. Do NOT include an iconography section in the stack document.
 
 ### 5. Backend Stack
 **Mark as N/A if this is a frontend-only or static site project**
@@ -129,9 +131,9 @@ You should:
 - Scaling approach
 
 #### CI/CD Pipeline
-- CI/CD platform (GitHub Actions, GitLab CI, Jenkins, etc.)
-- Pipeline stages
-- Deployment automation
+- CI/CD platform technology (GitHub Actions, GitLab CI, Jenkins, etc.) and rationale
+- Deployment automation and trigger configuration
+- **Note**: The stack defines *which CI/CD technology* is used. The pipeline structure (stages, gates, ordering) is defined in `gspec/practices.md`. Include platform-specific configuration details here (e.g., workflow YAML format, runner setup), not pipeline philosophy.
 
 #### Infrastructure as Code
 - IaC tool (Terraform, CloudFormation, Pulumi, etc.)
@@ -189,10 +191,13 @@ You should:
 
 ### 10. Testing Infrastructure
 
+> **The stack is the single authority for test tooling choices.** Define which frameworks and tools are used here. Testing philosophy, patterns, and coverage requirements are defined in `gspec/practices.md`.
+
 #### Testing Frameworks
-- Unit testing framework
+- Unit testing framework (Vitest, Jest, pytest, etc.) and rationale
 - Integration testing tools
-- E2E testing framework (Playwright, Cypress, etc.)
+- E2E testing framework (Playwright, Cypress, etc.) and rationale
+- Component testing tools (if applicable)
 
 #### Test Data Management
 - Test database strategy
@@ -219,7 +224,7 @@ You should:
 ### 12. Development Tools
 
 #### Package Management
-- Package manager (npm, yarn, pnpm, pip, maven, etc.)
+- **Package manager** — Explicitly declare the package manager (npm, yarn, pnpm, pip, maven, etc.) with rationale for the choice. This must be stated clearly so all other gspec commands and CI/CD configuration use the correct tool.
 - Dependency management strategy
 - Private package registry (if applicable)
 

package/commands/gspec.style.md

@@ -110,34 +110,27 @@ You should:
 - Component color adjustments
 - Contrast considerations
 
-#### Theme Switching
-- How themes interact with the color palette
-- Token mapping between themes
+### 6. Component Styling
 
-### 6. Components
+> **Focus on visual styling only** — colors, borders, typography, spacing, and state appearances. Do NOT define component structure, layout behavior, or interaction patterns (those belong in feature PRDs). The goal is to answer "what does it look like?" not "how does it work?"
 
 #### Buttons
-- Primary, secondary, tertiary styles
-- States (default, hover, active, disabled)
-- Sizes and padding
-- Border radius
+- Color treatments for primary, secondary, ghost variants
+- States: default, hover, active, disabled appearances
+- Sizes and border radius
 
 #### Form Elements
-- Input fields
-- Dropdowns, checkboxes, radio buttons
-- Labels and helper text
-- Validation states
+- Input field colors, borders, and focus ring styles
+- Label and helper text typography
+- Validation state colors (error, success)
 
 #### Cards & Containers
-- Background colors
-- Border styles
-- Shadow elevations
-- Corner radius
+- Background colors and border styles
+- Shadow elevations and corner radius
 
-#### Navigation
-- Header/navbar styles
-- Menu patterns
-- Active states
+#### Navigation Elements
+- Link colors: default, hover, active states
+- Background treatments for navigation surfaces
 
 ### 7. Visual Effects
 
@@ -157,11 +150,13 @@ You should:
 
 ### 8. Iconography
 
-#### Icon Style
-- Outlined vs filled
+> **The style guide is the single authority for icon library choices.** The stack document defines the CSS framework and component library (e.g., shadcn/ui); the style guide defines which icon set is used. This separation ensures icon decisions are driven by design rationale (visual consistency, stroke style) while component library decisions remain with the technology stack (framework compatibility).
+
+#### Icon Library
+- Specific icon library recommendation with rationale
+- Outlined vs filled style
 - Stroke width
 - Size standards
-- Icon library recommendation
 
 #### Usage Guidelines
 - When to use icons

package/dist/antigravity/gspec-analyze/SKILL.md

@@ -28,12 +28,11 @@ Read **every** available gspec document in this order:
 
 1. `gspec/profile.md` — Product identity, scope, audience, and positioning
 2. `gspec/stack.md` — Technology choices, frameworks, infrastructure
-3. `gspec/style.md` — Visual design language, tokens, component patterns
+3. `gspec/style.md` — Visual design language, tokens, component styling
 4. `gspec/practices.md` — Development standards, testing, conventions
 5. `gspec/architecture.md` — Technical blueprint: project structure, data model, API design, environment
 6. `gspec/research.md` — Competitive analysis and feature proposals
-7. `gspec/epics/*.md` — Epic structure and feature dependencies
-8. `gspec/features/*.md` — Individual feature requirements
+7. `gspec/features/*.md` — Individual feature requirements and dependencies
 
 If fewer than two spec files exist, inform the user that there is nothing to cross-reference and stop.
 
@@ -69,7 +68,6 @@ Systematically compare specs against each other. Look for these categories of di
 #### Scope & Priority Conflicts
 - A feature capability is marked P0 in one place but P1 or P2 in another
 - Profile describes scope or positioning that conflicts with what features actually define
-- Epic dependency ordering conflicts with feature priority levels
 - Research recommendations conflict with decisions already made in other specs
 
 #### Behavioral Conflicts

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

@@ -9,7 +9,7 @@ Your task is to take the established product specifications and produce a **Tech
 
 Beyond defining the architecture, you are also responsible for **identifying technical gaps and ambiguities** in the existing specs and **proposing implementation solutions**. This is the place in the gspec workflow where underspecified technical behavior is surfaced and resolved — so that `gspec-implement` can focus on building rather than making architectural decisions.
 
-This command is meant to be run **after** the foundation specs (profile, stack, style, practices) and feature specs (features, epics) are defined, and **before** `gspec-implement`.
+This command is meant to be run **after** the foundation specs (profile, stack, style, practices) and feature specs are defined, and **before** `gspec-implement`.
 
 You should:
 - Read all existing gspec documents first — this architecture must serve the product, stack, style, and features already defined
@@ -32,8 +32,7 @@ Before generating the architecture document, read **all** existing gspec documen
 2. **`gspec/stack.md`** — Technology choices, frameworks, and infrastructure. Use this as the basis for all technical decisions — framework conventions, database choice, API style, etc.
 3. **`gspec/style.md`** — Design system and tokens. Use this to inform frontend architecture, theming approach, and where design token files belong.
 4. **`gspec/practices.md`** — Development standards. Use this to align file organization, testing patterns, and code structure with team conventions.
-5. **`gspec/epics/*.md`** — Epic structure and feature dependencies. Use this to understand feature grouping and sequencing.
-6. **`gspec/features/*.md`** — Individual feature requirements. Use these to derive data entities, API endpoints, component structure, and integration points.
+5. **`gspec/features/*.md`** — Individual feature requirements and dependencies. Use these to derive data entities, API endpoints, component structure, and integration points.
 
 All of these provide essential context. If any are missing, note the gap and make reasonable assumptions — but flag them in the Open Decisions section.
 
@@ -46,7 +45,7 @@ All of these provide essential context. If any are missing, note the gap and mak
 - Begin the file with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.

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

@@ -1,11 +1,28 @@
 ---
 name: gspec-feature
-description: Generate a product requirements document (PRD) for an individual feature
+description: Generate one or more product requirements documents (PRDs) for features
 ---
 
 You are a senior Product Manager at a high-performing software company.
 
-Your task is to take the provided feature description (which may be vague or detailed) and produce a **Product Requirements Document (PRD)** that clearly defines *what* is being built and *why*, without deep technical or architectural implementation details.
+Your task is to take the provided feature description (which may be vague or detailed, small or large) and produce **one or more Product Requirements Documents (PRDs)** that clearly define *what* is being built and *why*, without deep technical or architectural implementation details.
+
+## Scope Assessment
+
+Before writing anything, assess whether the user's description is:
+
+1. **A single feature** — a focused piece of functionality that can be captured in one PRD (e.g., "user authentication", "CSV export", "dark mode support")
+2. **A large body of work** — something broad enough that it should be decomposed into multiple independent features (e.g., "a complete onboarding experience", "a full e-commerce checkout flow", "social features for the app")
+
+**If it's a single feature**, produce one PRD and save it to `gspec/features/`.
+
+**If it's large enough to warrant multiple features:**
+
+1. Propose a breakdown — list the distinct features you'd create, with a one-line description of each and their dependencies on each other
+2. **Ask the user to confirm, adjust, or reprioritize** the breakdown before writing any specs
+3. Once confirmed, generate a separate PRD for each feature in `gspec/features/`
+
+When in doubt, lean toward fewer features. Don't over-decompose — a feature should only be split out if it delivers independent user value and has a meaningfully different scope.
 
 ## Important: Agent-Oriented Documentation
 
@@ -62,19 +79,20 @@ Feature PRDs are designed to be **portable across projects**. A feature spec wri
 
 ## Output Rules
 
-- Output **ONLY** a single Markdown document
-- Save the file to the `gspec/features/` folder in the root of the project, create it if it doesn't exist
-- Name the file based on the feature (e.g., `user-authentication.md`, `dashboard-analytics.md`)
-- Begin the file with YAML frontmatter containing the gspec version:
+- Output one or more Markdown documents — **one per feature**
+- Save each file to the `gspec/features/` folder in the root of the project, create it if it doesn't exist
+- Name each file based on the feature (e.g., `user-authentication.md`, `dashboard-analytics.md`)
+- Begin each file with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.
-- **Before generating the document, you MUST resolve ambiguities through conversation.** Ask clarifying questions in the chat if:
+- **Before generating any document, you MUST resolve ambiguities through conversation.** Ask clarifying questions in the chat if:
   - The target users are unclear
   - The scope or boundaries of the feature are ambiguous
+  - The breakdown into multiple features is not obvious (for large requests)
   - Success criteria cannot be determined from the description
   - Priority or urgency is unspecified
   - Any assumption would materially change the shape of the spec
@@ -112,7 +130,7 @@ This separation — combined with the portability principles above — allows th
 
 ---
 
-## Required Sections
+## Required Sections (per feature PRD)
 
 **IMPORTANT**: Only include the sections listed below. Do NOT add additional sections such as "Technology Notes", "Implementation Details", "Technical Architecture", or any other custom sections. Stick strictly to this structure.
 
@@ -162,11 +180,23 @@ This separation — combined with the portability principles above — allows th
 
 ---
 
+## Multi-Feature Output
+
+When generating multiple features from a large request:
+
+- **Cross-reference dependencies** — each feature's Dependencies section should link to sibling features when applicable
+- **Maintain consistent terminology** — use the same terms for shared concepts across all generated PRDs
+- **Assign priorities holistically** — P0/P1/P2 levels should be consistent across the set (don't make everything P0)
+- **Suggest a build order** — after generating all PRDs, briefly note the recommended implementation sequence based on dependencies (e.g., "Build `user-authentication` first, then `user-profiles`, then `social-connections`")
+
+---
+
 ## Tone & Style
 
 - Clear, neutral, product-led
 - No fluff, no jargon
 - Designed to be skimmed
+- Consistent across all generated documents
 
 ---
 

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

@@ -7,13 +7,13 @@ You are a Senior Software Engineer and Tech Lead at a high-performing software c
 
 Your task is to take the project's **gspec specification documents** and use them to **implement the software**. You bridge the gap between product requirements and working code. You implement what the specs define — feature proposals and technical architecture suggestions belong earlier in the process (in `gspec-research` and `gspec-architect` respectively).
 
-**Features and epics are optional.** When `gspec/features/*.md` and `gspec/epics/*.md` exist, they guide implementation feature by feature. When they don't exist, you rely on the remaining gspec files (`profile.md`, `stack.md`, `style.md`, `practices.md`) combined with any prompting the user provides to the implement command. The user's prompt may describe what to build, specify a scope, or give high-level direction — treat it as your primary input alongside whatever gspec documents are available.
+**Features are optional.** When `gspec/features/*.md` exist, they guide implementation feature by feature. When they don't exist, you rely on the remaining gspec files (`profile.md`, `stack.md`, `style.md`, `practices.md`) combined with any prompting the user provides to the implement command. The user's prompt may describe what to build, specify a scope, or give high-level direction — treat it as your primary input alongside whatever gspec documents are available.
 
 You should:
 - Read and internalize all available gspec documents before writing any code
 - Implement incrementally, one logical unit at a time
 - Follow the project's defined stack, style, and practices exactly
-- **When no features or epics exist**, use the user's prompt and the remaining gspec files to determine what to build, then plan and implement incrementally
+- **When no features exist**, use the user's prompt and the remaining gspec files to determine what to build, then plan and implement incrementally
 
 ---
 
@@ -24,8 +24,7 @@ You should:
 Before writing any code, read all available gspec documents in this order:
 
 1. `gspec/profile.md` — Understand what the product is and who it's for
-2. `gspec/epics/*.md` — Understand the big picture and feature dependencies
-3. `gspec/features/*.md` — Understand individual feature requirements
+2. `gspec/features/*.md` — Understand individual feature requirements and dependencies
    > **Note:** Feature PRDs are designed to be portable and project-agnostic. They describe *what* behavior is needed without referencing specific personas, design systems, or technology stacks. During implementation, you resolve project-specific context by combining features with the profile, style, stack, and practices documents read in this phase.
 4. `gspec/stack.md` — Understand the technology choices
 5. `gspec/style.md` — Understand the visual design language
@@ -34,7 +33,7 @@ Before writing any code, read all available gspec documents in this order:
 
 If any of these files are missing, note what's missing and proceed with what's available.
 
-- **Features and epics are optional.** If `gspec/features/` and `gspec/epics/` are empty or don't exist, that's fine — the remaining gspec files plus the user's prompt to the implement command define what to build. Do not block on their absence or insist the user generate them first.
+- **Features are optional.** If `gspec/features/` is empty or doesn't exist, that's fine — the remaining gspec files plus the user's prompt to the implement command define what to build. Do not block on their absence or insist the user generate them first.
 - For other missing files (profile, stack, style, practices), note the gap and ask the user if they want to generate them first or proceed without them.
 
 #### Assess Implementation Status
@@ -52,8 +51,6 @@ For each feature PRD, build an implementation status summary:
 
 Present this summary to the user so they understand the starting point. If **all capabilities across all features are already checked**, inform the user and ask what they'd like to do — they may want to add new features, re-implement something, or they may be done.
 
-For epic summary files, check whether the features listed in the "Features Breakdown" section have checkboxes. A feature in an epic is considered complete when all its capabilities in the corresponding feature PRD are checked.
-
 ### Phase 2: Plan — Define the Build Order
 
 **Enter plan mode** and create a concrete, phased implementation plan.
@@ -108,13 +105,12 @@ Present a brief scaffold summary to the user before proceeding to feature implem
 
 1. **Announce the phase** — State which phase you're starting, what it covers, and what capabilities will be implemented
 2. **Implement the phase:**
-   a. **Follow the stack** — Use the exact technologies, frameworks, and patterns defined in `gspec/stack.md`
-   b. **Follow the practices** — Adhere to coding standards, testing requirements, and conventions from `gspec/practices.md`
-   c. **Follow the style** — Apply the design system, tokens, and component patterns from `gspec/style.md`
+   a. **Follow the stack** — Use the exact technologies, frameworks, and patterns defined in `gspec/stack.md`. The stack is the single authority for technology choices (testing tools, CI/CD platform, package manager). Where stack-specific practices (Section 15 of `stack.md`) conflict with general practices in `practices.md`, the stack's technology-specific guidance takes precedence for framework-specific concerns.
+   b. **Follow the practices** — Adhere to coding standards, testing philosophy, pipeline structure, and conventions from `gspec/practices.md`
+   c. **Follow the style** — Apply the design system, tokens, and icon library from `gspec/style.md`. The style is the single authority for icon library choices. Component libraries (e.g., shadcn/ui) are defined in `gspec/stack.md`.
    d. **Satisfy the requirements** — Trace each piece of code back to a functional requirement in the feature PRD (if available) or to the user's stated goals and the approved implementation plan
-3. **Mark capabilities as implemented** — After successfully implementing each capability, immediately update the feature PRD by changing its checkbox from `- [ ]` to `- [x]`. Do this incrementally as each capability is completed, not in a batch at the end. If a capability line did not have a checkbox prefix, add one as `- [x]`. This ensures that if the session is interrupted, progress is not lost. When updating gspec files, preserve existing `gspec-version` YAML frontmatter. If a file lacks frontmatter, add `---\ngspec-version: 1.6.0\n---` at the top.
-4. **Update epic status** — When all capabilities in a feature PRD are checked, update the corresponding feature's checkbox in the epic summary file (if one exists) from `- [ ]` to `- [x]`.
-5. **Run tests** — Execute the tests defined for this phase (and any existing tests to catch regressions). Fix any failures before proceeding.
+3. **Mark capabilities as implemented** — After successfully implementing each capability, immediately update the feature PRD by changing its checkbox from `- [ ]` to `- [x]`. Do this incrementally as each capability is completed, not in a batch at the end. If a capability line did not have a checkbox prefix, add one as `- [x]`. This ensures that if the session is interrupted, progress is not lost. When updating gspec files, preserve existing `gspec-version` YAML frontmatter. If a file lacks frontmatter, add `---\ngspec-version: 1.10.0\n---` at the top.
+4. **Run tests** — Execute the tests defined for this phase (and any existing tests to catch regressions). Fix any failures before proceeding.
 6. **Surface new gaps** — If implementation reveals new ambiguities, pause and consult the user rather than making silent assumptions
 7. **Pause and report** — After completing the phase and confirming tests pass, present a phase completion summary to the user:
 
@@ -158,21 +154,20 @@ When you encounter something the specs don't fully cover during implementation:
 
 ## Selecting What to Implement
 
-### When no features or epics exist:
+### When no features exist:
 
-If `gspec/features/` and `gspec/epics/` are empty or absent, use the **user's prompt** as the primary guide for what to build:
+If `gspec/features/` is empty or absent, use the **user's prompt** as the primary guide for what to build:
 
 1. **If the user provided a prompt** to the implement command, treat it as your primary directive. The prompt may describe a feature, a scope of work, a user story, or a high-level goal. Combine it with the remaining gspec files (profile, stack, style, practices) to plan and build.
 2. **If the user provided no prompt either**, use the product profile to identify a logical starting point — focus on the product's core value proposition and primary use cases. Suggest a starting point and confirm with the user.
 
-### When features and/or epics exist:
+### When features exist:
 
 **Filter by implementation status first.** Before selecting what to implement, assess which capabilities are already checked off (`[x]`) across all feature PRDs. Only unchecked capabilities (`[ ]` or no checkbox) are candidates for this run.
 
 If the user doesn't specify which feature to implement:
 
-1. Check `gspec/epics/*.md` for a phasing recommendation or build order
-2. **Focus on features with unchecked capabilities** — Features with all capabilities checked are complete and can be skipped
+1. **Focus on features with unchecked capabilities** — Features with all capabilities checked are complete and can be skipped
 3. Among features with pending work, prioritize unchecked P0 capabilities over P1, P1 over P2
 4. Respect dependency ordering — build foundations before dependent features
 5. Suggest a starting point and confirm with the user
@@ -181,9 +176,9 @@ If the user specifies a feature, focus on that feature's **unchecked capabilitie
 - Note any unmet dependencies
 - If the user explicitly asks to re-implement a checked capability, honor that request
 
-### When the user provides a prompt alongside existing features/epics:
+### When the user provides a prompt alongside existing features:
 
-The user's prompt takes priority for scoping. Use it to determine focus, and reference existing feature PRDs and epics as supporting context rather than the sole driver.
+The user's prompt takes priority for scoping. Use it to determine focus, and reference existing feature PRDs as supporting context rather than the sole driver.
 
 ---
 

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

@@ -5,7 +5,7 @@ description: Migrate existing gspec files to the current format when upgrading t
 
 You are a Technical Documentation Migration Specialist.
 
-Your task is to update existing gspec specification documents to match the current gspec format (version 1.6.0). You preserve all substantive content while ensuring documents follow the latest structural conventions.
+Your task is to update existing gspec specification documents to match the current gspec format (version 1.10.0). You preserve all substantive content while ensuring documents follow the latest structural conventions.
 
 ---
 
@@ -16,19 +16,19 @@ Your task is to update existing gspec specification documents to match the curre
 Scan the `gspec/` directory for all Markdown files:
 - `gspec/*.md` (profile, stack, style, practices, architecture)
 - `gspec/features/*.md` (individual feature PRDs)
-- `gspec/epics/*.md` (epic summaries)
+
 
 For each file, check the YAML frontmatter at the top of the file:
 - If the file starts with `---` followed by YAML content and another `---`, read the `gspec-version` field
 - If no frontmatter exists, the file predates version tracking
-- If `gspec-version` matches `1.6.0`, the file is current — skip it
+- If `gspec-version` matches `1.10.0`, the file is current — skip it
 
 Present an inventory to the user:
 
 > **gspec File Inventory:**
 > - `gspec/profile.md` — no version (needs migration)
 > - `gspec/stack.md` — version 1.0.3 (needs migration)
-> - `gspec/style.md` — version 1.6.0 (current, skipping)
+> - `gspec/style.md` — version 1.10.0 (current, skipping)
 > - `gspec/features/user-auth.md` — no version (needs migration)
 
 Ask the user to confirm which files to migrate, or confirm all.
@@ -45,7 +45,6 @@ For each file that needs migration, determine its document type and read the cor
 | `gspec/practices.md` | Development Practices | Read the `gspec-practices` skill definition |
 | `gspec/architecture.md` | Technical Architecture | Read the `gspec-architect` skill definition |
 | `gspec/features/*.md` | Feature PRD | Read the `gspec-feature` skill definition |
-| `gspec/epics/*.md` | Epic Summary | Read the `gspec-epic` skill definition |
 
 The skill definitions are located in your installed skills directory. Read them to understand the current "Required Sections" structure for each document type.
 
@@ -64,7 +63,7 @@ For each file to migrate:
 5. **Add or update the frontmatter** — Ensure the file starts with:
    ```
    ---
-   gspec-version: 1.6.0
+   gspec-version: 1.10.0
    ---
    ```
 6. **Present the proposed changes** to the user before writing. Show what sections are being reorganized, what is being added, and confirm no content is being lost.
@@ -78,7 +77,7 @@ After migrating all files:
 3. **Present a completion summary**:
 
 > **Migration Complete:**
-> - 4 files migrated to version 1.6.0
+> - 4 files migrated to version 1.10.0
 > - 2 files were already current (skipped)
 > - Content preserved in all files
 > - Sections reorganized: [list any structural changes]

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

@@ -25,7 +25,7 @@ You should:
 - Begin the file with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.
@@ -39,8 +39,10 @@ You should:
 - Focus on practices that matter for this specific project
 - Avoid generic advice that doesn't apply
 - **Do NOT include technology stack information** — this is documented separately
-- **Do NOT prescribe specific testing frameworks, tools, or libraries** — focus on testing principles, patterns, and practices, not which tools to use
+- **Do NOT prescribe specific testing frameworks, tools, or libraries** — focus on testing principles, patterns, and practices. The stack document (`gspec/stack.md`) is the single authority for which test tools are used.
+- **DO define CI/CD pipeline structure** — the practices document defines pipeline stages, gates, and ordering (lint → typecheck → test → build → deploy). The stack document defines which CI/CD platform technology is used (GitHub Actions, GitLab CI, etc.).
 - **Mark sections as "Not Applicable"** when they don't apply to this project
+- **Precedence rule**: Where this document conflicts with technology-specific practices in `gspec/stack.md`, the stack's technology-specific practices take precedence for framework-specific concerns (e.g., file naming conventions dictated by a framework). This document governs general engineering principles.
 
 ---
 

package/dist/antigravity/gspec-profile/SKILL.md

@@ -25,7 +25,7 @@ You should:
 - Begin the file with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.

package/dist/antigravity/gspec-research/SKILL.md

@@ -32,7 +32,7 @@ Before conducting any research, read available gspec documents for context:
    - **Market & Competition** section — direct competitors, indirect competitors or alternatives, white space or gaps the product fills
    - **Value Proposition** section — differentiation and competitive advantages
 2. `gspec/features/*.md` — **Optional.** If feature PRDs exist, read them to understand what capabilities are already specified. This enables gap analysis in later phases.
-3. `gspec/epics/*.md` — **Optional.** If epics exist, read them for broader product scope context.
+
 
 **If `gspec/profile.md` does not exist or has no Market & Competition section**, inform the user that a product profile with competitor information is required for competitive research. Suggest running `gspec-profile` first. Do not proceed without competitor information.
 
@@ -162,7 +162,7 @@ After writing `gspec/research.md`, ask the user:
    - Assumptions & Risks (assumptions, open questions, key risks and mitigations)
    - Success Metrics
    - Implementation Context (standard portability note)
-   - Begin the file with YAML frontmatter: `---\ngspec-version: 1.6.0\n---`
+   - Begin the file with YAML frontmatter: `---\ngspec-version: 1.10.0\n---`
 2. **Name the file** descriptively based on the feature (e.g., `gspec/features/csv-export.md`, `gspec/features/onboarding-wizard.md`)
 3. **Keep the PRD portable** — use generic role descriptions (not project-specific persona names), define success metrics in terms of the feature's own outcomes (not project-level KPIs), and describe UX behavior generically (not tied to a specific design system). The PRD should be reusable across projects.
 4. **Keep the PRD product-focused** — describe *what* and *why*, not *how*. Implementation details belong in the code, not the PRD.
@@ -181,7 +181,7 @@ After writing `gspec/research.md`, ask the user:
 - Begin `gspec/research.md` with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.
@@ -198,7 +198,7 @@ The `gspec/research.md` file must follow this structure:
 
 ```markdown
 ---
-gspec-version: 1.6.0
+gspec-version: 1.10.0
 ---
 
 # Competitive Research

package/dist/antigravity/gspec-stack/SKILL.md

@@ -25,7 +25,7 @@ You should:
 - Begin the file with YAML frontmatter containing the gspec version:
   ```
   ---
-  gspec-version: 1.6.0
+  gspec-version: 1.10.0
   ---
   ```
   The frontmatter must be the very first content in the file, before the main heading.
@@ -96,6 +96,8 @@ You should:
 - Responsive design tooling
 
 - **Note**: Visual design values (colors, typography, spacing) are documented separately as framework-agnostic design tokens; include here how the chosen CSS framework maps to those tokens
+- **Component library** (if applicable) — e.g., shadcn/ui, Headless UI, Radix UI. Component libraries are framework-specific technology choices and belong in the stack, not the style guide.
+- **Note**: Icon libraries (e.g., HeroIcons, Lucide) are defined in `gspec/style.md`, not here. The stack defines the CSS framework and component library; the style defines the icon set. Do NOT include an iconography section in the stack document.
 
 ### 5. Backend Stack
 **Mark as N/A if this is a frontend-only or static site project**
@@ -134,9 +136,9 @@ You should:
 - Scaling approach
 
 #### CI/CD Pipeline
-- CI/CD platform (GitHub Actions, GitLab CI, Jenkins, etc.)
-- Pipeline stages
-- Deployment automation
+- CI/CD platform technology (GitHub Actions, GitLab CI, Jenkins, etc.) and rationale
+- Deployment automation and trigger configuration
+- **Note**: The stack defines *which CI/CD technology* is used. The pipeline structure (stages, gates, ordering) is defined in `gspec/practices.md`. Include platform-specific configuration details here (e.g., workflow YAML format, runner setup), not pipeline philosophy.
 
 #### Infrastructure as Code
 - IaC tool (Terraform, CloudFormation, Pulumi, etc.)
@@ -194,10 +196,13 @@ You should:
 
 ### 10. Testing Infrastructure
 
+> **The stack is the single authority for test tooling choices.** Define which frameworks and tools are used here. Testing philosophy, patterns, and coverage requirements are defined in `gspec/practices.md`.
+
 #### Testing Frameworks
-- Unit testing framework
+- Unit testing framework (Vitest, Jest, pytest, etc.) and rationale
 - Integration testing tools
-- E2E testing framework (Playwright, Cypress, etc.)
+- E2E testing framework (Playwright, Cypress, etc.) and rationale
+- Component testing tools (if applicable)
 
 #### Test Data Management
 - Test database strategy
@@ -224,7 +229,7 @@ You should:
 ### 12. Development Tools
 
 #### Package Management
-- Package manager (npm, yarn, pnpm, pip, maven, etc.)
+- **Package manager** — Explicitly declare the package manager (npm, yarn, pnpm, pip, maven, etc.) with rationale for the choice. This must be stated clearly so all other gspec commands and CI/CD configuration use the correct tool.
 - Dependency management strategy
 - Private package registry (if applicable)