gspec 1.17.1 → 1.19.0

package/dist/opencode/skills/gspec-migrate/SKILL.md

@@ -0,0 +1,142 @@
+---
+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.
+
+Your task is to update existing gspec specification documents to match the current spec format (spec-version v1). You preserve all substantive content while ensuring documents follow the latest structural conventions.
+
+---
+
+## Workflow
+
+### Phase 1: Inventory — Scan All gspec Files
+
+Scan the `gspec/` directory for all spec files:
+- `gspec/*.md` (profile, stack, style, practices, architecture)
+- `gspec/style.html` (HTML design system, if present — the style guide may be in either Markdown or HTML)
+- `gspec/features/*.md` (individual feature PRDs)
+- `gspec/features/*.plan.md` (plan files; legacy `*.tasks.md` files are also scanned and renamed — see Migration Rules below)
+
+Do **not** migrate files under `gspec/design/` — those are external design mockups (HTML, SVG, PNG, JPG) that are dropped in manually and are not owned by gspec. Leave them untouched.
+
+For each file, check the spec-version metadata:
+- **For Markdown files**: check the YAML frontmatter at the top. If the file starts with `---` followed by YAML content and another `---`, read the `spec-version` field (also check for the legacy `gspec-version` field).
+- **For `gspec/style.html`**: the spec-version is stored as the first-line HTML comment `<!-- spec-version: ... -->`. Read that comment.
+- If no version metadata exists, the file predates version tracking
+- If `spec-version` matches `v1`, the file is current — skip it
+- If a Markdown file has `gspec-version` (old field name) instead of `spec-version`, it needs migration regardless of value
+
+Present an inventory to the user:
+
+> **gspec File Inventory:**
+> - `gspec/profile.md` — no version (needs migration)
+> - `gspec/stack.md` — gspec-version 1.0.3 (needs migration — old field name)
+> - `gspec/style.html` — spec-version v1 (current, skipping)
+> - `gspec/features/user-auth.md` — no version (needs migration)
+
+Ask the user to confirm which files to migrate, or confirm all.
+
+### Phase 2: Reference — Read Current Format Definitions
+
+For each file that needs migration, determine its document type and read the corresponding gspec command skill to understand the current expected format:
+
+| gspec File | Document Type | Format Reference |
+|---|---|---|
+| `gspec/profile.md` | Product Profile | Read the `gspec-profile` skill definition |
+| `gspec/stack.md` | Technology Stack | Read the `gspec-stack` skill definition |
+| `gspec/style.md` or `gspec/style.html` | Visual Style Guide (Markdown or HTML) | Read the `gspec-style` skill definition |
+| `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 |
+
+The skill definitions are located in your installed skills directory. Read them to understand the current "Required Sections" structure for each document type.
+
+### Phase 3: Migrate — Update Each File
+
+For each file to migrate:
+
+1. **Read the current file content** — Understand what information it contains
+2. **Read the format reference** — Understand the expected structure from the corresponding skill definition
+3. **Compare structures** — Identify:
+   - Sections that exist in both (may need renaming, reordering, or reformatting)
+   - Sections that are new in the current format (add with content from existing file where applicable, or mark as "To be defined")
+   - Sections that were removed in the current format (move content to the appropriate new section, or remove if truly obsolete)
+   - Formatting changes (e.g., checkbox format for capabilities, acceptance criteria requirements)
+4. **Preserve all substantive content** — Never discard information during migration. If a section was removed from the format, find the right place for its content or keep it in a "Legacy Content" section at the bottom.
+5. **Add or update the version metadata** —
+   - **For Markdown files**, ensure the file starts with:
+     ```
+     ---
+     spec-version: v1
+     ---
+     ```
+     If the file has the old `gspec-version` field, rename it to `spec-version` and set the value to `v1`.
+   - **For `gspec/style.html`**, ensure the very first line of the file is:
+     ```
+     <!-- spec-version: v1 -->
+     ```
+     This comment must appear before the `<!DOCTYPE html>` declaration. If the file already has a `<!-- spec-version: ... -->` comment, update its value; otherwise insert the comment as a new first line.
+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.
+
+### Phase 4: Verify — Confirm Migration
+
+After migrating all files:
+
+1. **Verify every migrated file** has the correct frontmatter (`spec-version: v1`)
+2. **Verify no content was lost** — Briefly summarize what was preserved and any content that was relocated
+3. **Present a completion summary**:
+
+> **Migration Complete:**
+> - 4 files migrated to spec-version v1
+> - 2 files were already current (skipped)
+> - Content preserved in all files
+> - Sections reorganized: [list any structural changes]
+
+---
+
+## Migration Rules
+
+**Content preservation is paramount.** The user's information must never be discarded. If the format changes eliminated a section, find the right home for that content in the new structure.
+
+**Maintain document voice.** Each gspec document was written with a specific tone and style. Restructure and reformat, but do not rewrite prose unless the meaning would be lost.
+
+**Handle feature PRD capabilities carefully.** If migrating feature PRDs:
+- Preserve checkbox states (`[x]` and `[ ]`) exactly as they are
+- If capabilities lack checkboxes (old format), add unchecked checkboxes
+- If capabilities lack acceptance criteria (current format requires them), add placeholder criteria: "Acceptance criteria to be defined"
+- Preserve priority levels (P0, P1, P2)
+
+**Rename legacy `*.tasks.md` plan files to `*.plan.md`.** Before gspec renamed the `tasks` skill to `plan`, plan files lived at `gspec/features/<feature>.tasks.md`. During migration:
+- For every `gspec/features/*.tasks.md` file, rename it to `gspec/features/<same-slug>.plan.md` (use `git mv` when the project is a git repo so history is preserved; otherwise plain move)
+- Inside the renamed file, update the top-of-file heading from `# Tasks: <Feature Name>` to `# Plan: <Feature Name>` and the section heading from `## Tasks` to `## Plan`. Leave everything else (frontmatter, task IDs, `[P]` markers, `deps:`, `covers:`, checkbox states) unchanged
+- Preserve task IDs verbatim — `T1`, `T2`, etc. remain stable; do not renumber
+- Confirm the rename plan with the user before applying, in the same approval flow as other migrations
+
+**Handle missing sections gracefully.** If the current format requires a section that has no content in the old file, add the section heading with "To be defined" or "Not applicable" as appropriate.
+
+**Frontmatter handling (Markdown files):**
+- If the file has no frontmatter, add it at the very top
+- If the file has the old `gspec-version` field, rename it to `spec-version`
+- If the file has frontmatter without `spec-version`, add the field
+- If the file has an outdated `spec-version`, update it
+- Preserve any other frontmatter fields that may exist
+
+**HTML version-comment handling (`gspec/style.html`):**
+- If the file has no `<!-- spec-version: ... -->` comment, insert one as the first line of the file (before `<!DOCTYPE html>`)
+- If the file has an outdated spec-version in the comment, update the value in place
+- Do not move, wrap, or reformat the comment — it must remain on the first line exactly as `<!-- spec-version: <value> -->`
+
+---
+
+## Tone & Style
+
+- Precise and careful — migration is a delicate operation
+- Transparent — show every change before making it
+- Conservative — when in doubt, preserve rather than discard
+
+---
+
+## Input
+

package/dist/{codex/gspec-tasks → opencode/skills/gspec-plan}/SKILL.md

@@ -1,13 +1,13 @@
 ---
-name: gspec-tasks
-description: Decompose a feature PRD in gspec/features/ into an ordered, dependency-aware task plan with parallel-execution markers, written to gspec/features/<feature>.tasks.md. 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. "break this feature into tasks", "what order should I build this in", "plan the implementation order", "make a task list for X", "what can run in parallel", "decompose feature Y", "ordered task 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.
 
-Your task is to take a **feature PRD** from `gspec/features/` and decompose it into an **ordered, dependency-aware task plan** with parallel-execution markers. The output is a separate sibling file at `gspec/features/<feature>.tasks.md` that `gspec-implement` consumes during its planning phase.
+Your task is to take a **feature PRD** from `gspec/features/` and decompose it into an **ordered, dependency-aware plan** with parallel-execution markers. The output is a separate sibling file at `gspec/features/<feature>.plan.md` that `gspec-implement` consumes as its build order.
 
-The PRD answers *what* and *why*. The tasks file answers *how* and *in what order*.
+The PRD answers *what* and *why*. The plan file answers *how* and *in what order*.
 
 ## When to Run This Skill
 
@@ -24,8 +24,8 @@ Skip this skill for trivial features — `gspec-implement`'s checkbox-driven pla
 ## Inputs
 
 - **Required**: a feature PRD at `gspec/features/<feature>.md` (the user names the feature; if ambiguous, ask)
-- **Supporting context** (read but don't quote): `gspec/architecture.md`, `gspec/stack.md`. Use these only to inform task granularity and ordering — never to embed project-specific technology choices into the tasks file
-- **Existing tasks file** (if any) at `gspec/features/<feature>.tasks.md` — if present and non-empty, treat it as authoritative state and refuse to overwrite without explicit user confirmation
+- **Supporting context** (read but don't quote): `gspec/architecture.md`, `gspec/stack.md`. Use these only to inform task granularity and ordering — never to embed project-specific technology choices into the plan file
+- **Existing plan file** (if any) at `gspec/features/<feature>.plan.md` — if present and non-empty, treat it as authoritative state and refuse to overwrite without explicit user confirmation
 
 ---
 
@@ -35,7 +35,7 @@ Skip this skill for trivial features — `gspec-implement`'s checkbox-driven pla
 
 1. Read the target feature PRD in full. Extract every capability and its acceptance criteria.
 2. Read `gspec/architecture.md` and `gspec/stack.md` for ordering signals (e.g., schema must exist before API; API before UI).
-3. If a tasks file already exists for this feature, read it. Decide whether the user wants to (a) regenerate from scratch, (b) add tasks for newly added capabilities only, or (c) abort. Ask before proceeding.
+3. If a plan file already exists for this feature, read it. Decide whether the user wants to (a) regenerate from scratch, (b) add tasks for newly added capabilities only, or (c) abort. Ask before proceeding.
 
 ### Phase 2: Decompose
 
@@ -60,26 +60,28 @@ For each unchecked PRD capability:
 
 ### Phase 4: Plan-Mode Confirmation
 
-Enter plan mode and present the proposed tasks file content to the user. Show:
+Enter plan mode and present the proposed plan file content to the user. Show:
 
 - Total task count and how many `[P]`-marked
 - The full proposed file body
 - Any capabilities you could not decompose (explain why)
-- Any cross-feature dependencies you noticed (the user may want to address them in another feature's tasks file)
+- Any cross-feature dependencies you noticed (the user may want to address them in another feature's plan file)
 
 Wait for approval. The user may edit individual tasks, change ordering, drop or add `[P]` markers, or split/merge tasks.
 
+The user's approval here is what lets `gspec-implement` skip its own plan-mode step when it later consumes this file. Be deliberate — the plan you write here is the build order.
+
 ### Phase 5: Write
 
-After approval, write `gspec/features/<feature>.tasks.md`. Never overwrite a non-empty existing file without explicit user confirmation in Phase 1.
+After approval, write `gspec/features/<feature>.plan.md`. Never overwrite a non-empty existing file without explicit user confirmation in Phase 1.
 
-When writing, preserve any existing `spec-version` frontmatter from the prior tasks file. New files use `spec-version: v1`.
+When writing, preserve any existing `spec-version` frontmatter from the prior plan file. New files use `spec-version: v1`.
 
 ---
 
 ## Output Format
 
-The tasks file has YAML frontmatter and a single `## Tasks` section.
+The plan file has YAML frontmatter and a single `## Plan` section.
 
 ```markdown
 ---
@@ -87,9 +89,9 @@ spec-version: v1
 feature: <feature-slug>
 ---
 
-# Tasks: <Feature Name>
+# Plan: <Feature Name>
 
-## Tasks
+## Plan
 
 - [ ] **T1** [P] **P0** scaffold the Astro page route at `src/pages/index.astro`
   - deps: —
@@ -123,19 +125,19 @@ feature: <feature-slug>
 
 ## Relationship to PRD Checkboxes
 
-The tasks file and the PRD use **separate checkboxes**:
+The plan file and the PRD use **separate checkboxes**:
 
-- **Task checkboxes** (`- [ ]` / `- [x]` in the tasks file) track *execution state* — flip when the task is done.
+- **Task checkboxes** (`- [ ]` / `- [x]` in the plan file) track *execution state* — flip when the task is done.
 - **Capability checkboxes** (`- [ ]` / `- [x]` in the PRD) track *delivery state* — only flip when **every** task whose `covers:` references that capability is complete.
 
-`gspec-implement` is responsible for keeping both in sync. This skill only writes the initial unchecked tasks file.
+`gspec-implement` is responsible for keeping both in sync. This skill only writes the initial unchecked plan file.
 
 ---
 
 ## Output Rules
 
-- **Use plan mode** in Phase 4. Never write the tasks file before the user approves.
-- One tasks file per feature. Co-located with the PRD as `gspec/features/<feature>.tasks.md`.
+- **Use plan mode** in Phase 4. Never write the plan file before the user approves.
+- One plan file per feature. Co-located with the PRD as `gspec/features/<feature>.plan.md`.
 - Begin each file with the YAML frontmatter shown above.
 - Preserve existing frontmatter and existing task IDs when regenerating — append new tasks rather than renumbering.
 - If you discover the PRD itself is ambiguous (a capability has no clear acceptance criteria), pause and recommend the user run `gspec-feature` to refine the PRD before continuing. Do not invent acceptance criteria.

package/dist/opencode/{gspec-practices → skills/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/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.17.1",
+    "version": "1.19.0",
     "description": "Install gspec specification commands for Claude Code, Cursor, and other AI tools",
     "main": "bin/gspec.js",
     "type": "module",

package/templates/spec-sync.md

@@ -13,7 +13,7 @@ Use this mapping whenever the user's intent matches:
 - **Building, implementing, coding, scaffolding, shipping, or "making it real"** — invoke `gspec-implement`. This is the most commonly-missed skill. If the user asks you to write code for anything the specs describe (or a new capability that should be specced), route through `gspec-implement` rather than editing files directly. Generic prompts like "build it", "go", "keep going", "continue", or "do the next phase" should also invoke it when recent conversation has been about specs or planning.
 - **Defining the product, users, or vision** — invoke `gspec-profile`.
 - **Planning or writing a new feature / PRD** — invoke `gspec-feature`.
-- **Producing an ordered task plan from a feature PRD (with explicit dependencies and parallel-execution markers)** — invoke `gspec-tasks`. Run before `gspec-implement` for non-trivial features.
+- **Producing an ordered plan from a feature PRD (with explicit dependencies and parallel-execution markers)** — invoke `gspec-plan`. Run before `gspec-implement` for non-trivial features; when a plan file exists, `gspec-implement` skips its own plan-mode step.
 - **Choosing or revising the tech stack** — invoke `gspec-stack`.
 - **Defining visual design, tokens, or theme** — invoke `gspec-style`.
 - **Setting coding standards, testing, or workflow conventions** — invoke `gspec-practices`.
@@ -25,13 +25,17 @@ Use this mapping whenever the user's intent matches:
 
 If the user explicitly asks you to skip the skill and just do the work, honor that — but by default, prefer the skill.
 
+### Asking the user multiple questions
+
+When a skill needs feedback on more than one question, first preview all of them as a numbered list so the user knows the full scope, then ask them **one at a time** in the conversation. Never present multiple questions as a single numbered list expecting one combined reply — that forces the user to retype each question number alongside their answer. One question per turn keeps replies short and natural.
+
 ### When you make code changes, follow these rules:
 
 1. **Read the specs first** — Before making non-trivial changes, read the relevant gspec documents to understand existing decisions and constraints. At minimum, scan `gspec/profile.md` and any feature PRDs in `gspec/features/` related to your work.
 
 2. **Spec before you build** — If the user asks for a feature or capability that isn't covered by an existing feature PRD in `gspec/features/`, run the `gspec-feature` command to create a new feature PRD before implementing it. Every feature should be specified before it's built — don't skip straight to code.
 
-3. **Update feature checkboxes** — When you implement a capability defined in a feature PRD (`gspec/features/*.md`), change its checkbox from `- [ ]` to `- [x]`. **If a tasks file exists** at `gspec/features/<feature>.tasks.md`, also flip the checkbox of each completed task in that file. Only flip the PRD capability checkbox once every task whose `covers:` references it is checked.
+3. **Update feature checkboxes** — When you implement a capability defined in a feature PRD (`gspec/features/*.md`), change its checkbox from `- [ ]` to `- [x]`. **If a plan file exists** at `gspec/features/<feature>.plan.md`, also flip the checkbox of each completed task in that file. Only flip the PRD capability checkbox once every task whose `covers:` references it is checked.
 
 4. **Update specs that your changes contradict** — If your code change makes a spec statement incorrect (e.g., you changed the data model, switched a dependency, altered a UI pattern, or added a new API endpoint), update the spec to reflect reality. Common candidates:
    - `gspec/architecture.md` — project structure, data model, API routes, component hierarchy

package/dist/opencode/gspec-tasks/SKILL.md

@@ -1,154 +0,0 @@
----
-name: gspec-tasks
-description: Decompose a feature PRD in gspec/features/ into an ordered, dependency-aware task plan with parallel-execution markers, written to gspec/features/<feature>.tasks.md. 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. "break this feature into tasks", "what order should I build this in", "plan the implementation order", "make a task list for X", "what can run in parallel", "decompose feature Y", "ordered task 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.
----
-
-You are a Senior Engineering Lead at a high-performing software company.
-
-Your task is to take a **feature PRD** from `gspec/features/` and decompose it into an **ordered, dependency-aware task plan** with parallel-execution markers. The output is a separate sibling file at `gspec/features/<feature>.tasks.md` that `gspec-implement` consumes during its planning phase.
-
-The PRD answers *what* and *why*. The tasks file answers *how* and *in what order*.
-
-## When to Run This Skill
-
-Run after `gspec-feature` and before `gspec-implement` when:
-
-- The feature is large enough that build order matters (more than 3-4 capabilities, or non-trivial cross-capability dependencies)
-- Work could be parallelized and you want that surfaced explicitly
-- You want a reviewable execution plan before code is written
-
-Skip this skill for trivial features — `gspec-implement`'s checkbox-driven planning is sufficient there.
-
----
-
-## Inputs
-
-- **Required**: a feature PRD at `gspec/features/<feature>.md` (the user names the feature; if ambiguous, ask)
-- **Supporting context** (read but don't quote): `gspec/architecture.md`, `gspec/stack.md`. Use these only to inform task granularity and ordering — never to embed project-specific technology choices into the tasks file
-- **Existing tasks file** (if any) at `gspec/features/<feature>.tasks.md` — if present and non-empty, treat it as authoritative state and refuse to overwrite without explicit user confirmation
-
----
-
-## Workflow
-
-### Phase 1: Discovery
-
-1. Read the target feature PRD in full. Extract every capability and its acceptance criteria.
-2. Read `gspec/architecture.md` and `gspec/stack.md` for ordering signals (e.g., schema must exist before API; API before UI).
-3. If a tasks file already exists for this feature, read it. Decide whether the user wants to (a) regenerate from scratch, (b) add tasks for newly added capabilities only, or (c) abort. Ask before proceeding.
-
-### Phase 2: Decompose
-
-For each unchecked PRD capability:
-
-1. Propose **1–N tasks** that, taken together, satisfy the capability's acceptance criteria.
-2. Tasks should be small enough that a single implementation pass can complete and verify each one (typically 1-3 files, 1-3 acceptance criteria worth of work).
-3. Carry the capability's priority (`P0`/`P1`/`P2`) onto each task.
-4. Record the **`covers:` line** verbatim — quote the capability text from the PRD so the trace is unambiguous. A single task may cover multiple capabilities; a single capability may be covered by multiple tasks.
-
-### Phase 3: Order & Mark Parallelism
-
-1. Identify dependencies. A task depends on another when:
-   - It writes files the other reads or extends
-   - It uses APIs/types/schemas the other introduces
-   - It tests behavior the other implements
-2. Emit a **topological ordering**: list tasks in an order where every `deps:` reference points strictly backwards.
-3. Mark a task `[P]` (parallel-safe) only when it satisfies **both** conditions:
-   - Its `deps:` are all already complete (i.e., earlier in the list and not currently in flight beside it)
-   - It does not write to the same files as another `[P]`-marked sibling at the same level
-   When in doubt, leave `[P]` off. False parallelism causes more pain than missed parallelism.
-
-### Phase 4: Plan-Mode Confirmation
-
-Enter plan mode and present the proposed tasks file content to the user. Show:
-
-- Total task count and how many `[P]`-marked
-- The full proposed file body
-- Any capabilities you could not decompose (explain why)
-- Any cross-feature dependencies you noticed (the user may want to address them in another feature's tasks file)
-
-Wait for approval. The user may edit individual tasks, change ordering, drop or add `[P]` markers, or split/merge tasks.
-
-### Phase 5: Write
-
-After approval, write `gspec/features/<feature>.tasks.md`. Never overwrite a non-empty existing file without explicit user confirmation in Phase 1.
-
-When writing, preserve any existing `spec-version` frontmatter from the prior tasks file. New files use `spec-version: v1`.
-
----
-
-## Output Format
-
-The tasks file has YAML frontmatter and a single `## Tasks` section.
-
-```markdown
----
-spec-version: v1
-feature: <feature-slug>
----
-
-# Tasks: <Feature Name>
-
-## Tasks
-
-- [ ] **T1** [P] **P0** scaffold the Astro page route at `src/pages/index.astro`
-  - deps: —
-  - covers: "Page displays a clear tagline and one-line value proposition that communicates what gspec does"
-- [ ] **T2** **P0** wire CTA copy-to-clipboard interaction
-  - deps: T1
-  - covers: "Page displays a prominent install CTA with the install command"
-- [ ] **T3** [P] **P1** add the workflow diagram component
-  - deps: T1
-  - covers: "Page explains the gspec workflow in three or fewer steps"
-```
-
-### Field rules
-
-- **ID**: `T<n>`, monotonically increasing from `T1`. IDs are stable — never renumber existing tasks during a regenerate; append new ones with the next free number.
-- **`[P]`**: optional parallel marker. Place between the ID and the priority.
-- **Priority**: `P0`, `P1`, or `P2`, matching the source capability.
-- **Description**: one short imperative sentence. Concrete files or modules where useful, but no implementation code.
-- **`deps:`**: comma-separated task IDs. Use `—` (em dash) when there are no dependencies.
-- **`covers:`**: capability text from the PRD, quoted. For tasks covering multiple capabilities, separate quoted strings with `; `.
-
-### What NOT to write
-
-- ❌ No code blocks or pseudocode — that belongs in the implementation step.
-- ❌ No technology choices not already in `stack.md` or `architecture.md`.
-- ❌ No timeline estimates (hours, days, sprints) — see `gspec-feature` for the same rule.
-- ❌ No tasks for capabilities that are already `- [x]` in the PRD, unless the user explicitly requests re-implementation.
-- ❌ No "review" or "documentation" tasks unless the PRD's acceptance criteria explicitly require them.
-
----
-
-## Relationship to PRD Checkboxes
-
-The tasks file and the PRD use **separate checkboxes**:
-
-- **Task checkboxes** (`- [ ]` / `- [x]` in the tasks file) track *execution state* — flip when the task is done.
-- **Capability checkboxes** (`- [ ]` / `- [x]` in the PRD) track *delivery state* — only flip when **every** task whose `covers:` references that capability is complete.
-
-`gspec-implement` is responsible for keeping both in sync. This skill only writes the initial unchecked tasks file.
-
----
-
-## Output Rules
-
-- **Use plan mode** in Phase 4. Never write the tasks file before the user approves.
-- One tasks file per feature. Co-located with the PRD as `gspec/features/<feature>.tasks.md`.
-- Begin each file with the YAML frontmatter shown above.
-- Preserve existing frontmatter and existing task IDs when regenerating — append new tasks rather than renumbering.
-- If you discover the PRD itself is ambiguous (a capability has no clear acceptance criteria), pause and recommend the user run `gspec-feature` to refine the PRD before continuing. Do not invent acceptance criteria.
-
----
-
-## Tone & Style
-
-- Decisive — pick an ordering and defend it; don't list options.
-- Tight — every task line earns its place.
-- Honest about dependencies — it's better to be slightly conservative on `[P]` than to claim parallelism that doesn't hold.
-
----
-
-## Input Feature
-