gspec 1.16.0 → 1.17.1

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

@@ -191,6 +191,16 @@ When generating multiple features from a large request:
 
 ---
 
+## After Writing the PRD
+
+After saving each PRD, end your response with a brief next-step pointer:
+
+> *For larger features, run `/gspec-tasks <feature-slug>` to produce an ordered task plan with explicit dependencies and parallel-execution markers before running `/gspec-implement`. Trivial features can skip straight to `/gspec-implement`.*
+
+This is a one-line nudge, not a prompt — do not generate the tasks file from this skill, and do not block the user on it.
+
+---
+
 ## Tone & Style
 
 - Clear, neutral, product-led

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

@@ -26,6 +26,7 @@ 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/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.
+3. `gspec/features/*.tasks.md` — For any feature in scope, also read its tasks file if one exists. Tasks files are produced by `gspec-tasks` and contain an ordered, dependency-aware breakdown of the PRD's capabilities into concrete implementation tasks with `[P]` parallel markers and explicit `deps:` lines. **When a tasks file exists, it is the authoritative build order for that feature.** When it doesn't exist, fall back to the PRD's checkbox capabilities directly.
 4. `gspec/stack.md` — Understand the technology choices
 5. `gspec/style.md` **or** `gspec/style.html` — Understand the visual design language. The style guide may be in either format; read whichever exists (or both, if both are present — the HTML file contains the renderable token definitions and visual examples, the Markdown file contains prose rationale)
 6. `gspec/design/**` — If this folder exists, read every mockup in it. Supported formats include HTML pages, SVG files, and image files (PNG, JPG, WEBP). These are visual mockups (typically produced by external design tools like Figma, v0, Framer AI, etc.) that show layout, composition, and visual intent for specific screens or flows. **Treat them as authoritative visual guidance** — when building UI for a feature, look for relevant mockups in `gspec/design/` and match their layout, spacing, and hierarchy within the constraints of the style guide
@@ -46,10 +47,16 @@ This command is designed to be **run multiple times** as features are added or e
 - **`- [ ]`** (unchecked) = capability not yet implemented — include in this run's scope
 - **No checkbox prefix** = treat as not yet implemented (backwards compatible with older PRDs)
 
+**When a feature has a tasks file** (`gspec/features/<feature>.tasks.md`), also assess task-level state:
+
+- A task with `- [x]` is complete; skip unless user requests re-implementation
+- A task with `- [ ]` is pending and goes into this run's scope
+- A capability is considered fully delivered only when **every** task whose `covers:` references it is `- [x]`. A PRD capability checkbox should never be checked while one of its covering tasks is still unchecked, and vice versa — flag any such inconsistency to the user
+
 For each feature PRD, build an implementation status summary:
 
-> **Feature: User Authentication** — 4/7 capabilities implemented (all P0 done, 3 P1/P2 remaining)
-> **Feature: Dashboard** — 0/5 capabilities implemented (new feature)
+> **Feature: User Authentication** — 4/7 capabilities implemented (all P0 done, 3 P1/P2 remaining); tasks file shows 8/14 tasks done
+> **Feature: Dashboard** — 0/5 capabilities implemented (new feature, no tasks file)
 
 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.
 
@@ -57,14 +64,15 @@ Present this summary to the user so they understand the starting point. If **all
 
 **Enter plan mode** and create a concrete, phased implementation plan.
 
-1. **Survey the full scope** — Review all feature PRDs and identify every unchecked capability that is in scope for this run
-2. **Organize into implementation phases** — Group related capabilities into logical phases that can be built and verified independently. Each phase should:
+1. **Survey the full scope** — Review all feature PRDs and identify every unchecked capability that is in scope for this run. For features that have a tasks file, the unchecked tasks (not just capabilities) are the actual unit of work.
+2. **Organize into implementation phases** — Group related work into logical phases that can be built and verified independently. Each phase should:
    - Have a clear name and objective (e.g., "Phase 1: Core Data Models & API", "Phase 2: Authentication Flow")
-   - List the specific capabilities (with feature PRD references) it will implement
+   - List the specific capabilities (with feature PRD references) it will implement, **and the specific tasks (by ID, e.g. T1, T2, T7) when a tasks file exists**
    - Identify files to create or modify
    - Note dependencies on prior phases
    - Include an estimated scope (small/medium/large)
-3. **Account for every unchecked capability** — The plan must explicitly place every unchecked capability from in-scope feature PRDs into a phase **or** list it under a "Proposed to Defer" section with a reason. No unchecked capability may be silently omitted from the plan. The user reviews and approves what gets deferred at plan approval time.
+   - **When tasks files exist for in-scope features**, respect the `deps:` ordering they declare (no task may be scheduled before its declared deps), and note `[P]`-marked tasks as parallel-safe within a phase so the phase can fan-out work where appropriate
+3. **Account for every unchecked unit of work** — The plan must explicitly place every unchecked capability (or every unchecked task, when a tasks file exists) from in-scope feature PRDs into a phase **or** list it under a "Proposed to Defer" section with a reason. Nothing unchecked may be silently omitted from the plan. The user reviews and approves what gets deferred at plan approval time.
 4. **Define test expectations per phase** — For each phase, specify what tests will be run to verify correctness before moving on (unit tests, integration tests, build verification, etc.)
 5. **Present the plan** — Show the user the full phased plan with clear phase boundaries and ask for approval
 
@@ -113,7 +121,10 @@ Present a brief scaffold summary to the user before proceeding to feature implem
    c. **Follow the style** — Apply the design system, tokens, and icon library from `gspec/style.md` or `gspec/style.html` (whichever exists). The style guide is the single authority for icon library choices. Component libraries (e.g., shadcn/ui) are defined in `gspec/stack.md`.
    d. **Match the mockups** — For UI work, if `gspec/design/` contains mockups relevant to the screen or flow you are building, match their layout, spacing, and visual hierarchy. Resolve any conflict between a mockup and the style guide in favor of the style guide's tokens and semantics, then adjust the layout to remain faithful to the mockup's intent. If a mockup shows a visual pattern that the style guide doesn't cover, pause and ask the user whether to extend the style guide or deviate from the mockup.
    e. **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 `spec-version` YAML frontmatter. If a file lacks frontmatter, add `---\nspec-version: v1\n---` at the top.
+3. **Mark progress as you go** — Update checkboxes incrementally, never in a batch at the end. This ensures that if the session is interrupted, progress is not lost.
+   - **Tasks (when a tasks file exists)**: as soon as a task is complete and verified, flip its checkbox in `gspec/features/<feature>.tasks.md` from `- [ ]` to `- [x]`.
+   - **Capabilities**: flip a PRD capability checkbox from `- [ ]` to `- [x]` only after every task whose `covers:` references it is checked. If no tasks file exists for that feature, flip the capability checkbox immediately on completion (the original behavior). If a capability line did not have a checkbox prefix, add one as `- [x]`.
+   - When updating gspec files, preserve existing `spec-version` YAML frontmatter. If a file lacks frontmatter, add `---\nspec-version: v1\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:
@@ -134,7 +145,7 @@ After implementation:
 2. **Review against acceptance criteria** — For each capability in the feature PRDs, check that every acceptance criterion listed under it is satisfied. These sub-listed conditions are the definition of "done" for each capability. If any criterion is not met, the capability should not be marked `[x]`.
 3. **Check the Definition of Done** from `gspec/practices.md`
 4. **Verify no unapproved deferrals** — Compare the final implementation against the approved plan. If any capability that was assigned to a phase was not implemented, **do not silently leave it unchecked**. Flag it to the user, explain why it wasn't completed, and get explicit approval before marking it as deferred. Only capabilities the user approved for deferral during planning (or explicitly approves now) may remain unchecked.
-5. **Verify checkbox accuracy** — Confirm that every capability marked `[x]` in the feature PRDs is genuinely implemented and working. Confirm that capabilities left as `[ ]` were approved for deferral by the user. Present a final status summary:
+5. **Verify checkbox accuracy** — Confirm that every capability marked `[x]` in the feature PRDs is genuinely implemented and working. Confirm that capabilities left as `[ ]` were approved for deferral by the user. **For features with tasks files**, also confirm task↔capability consistency: every checked capability has all its covering tasks checked, and every unchecked capability has at least one unchecked covering task. Present a final status summary:
 
 > **Implementation Summary:**
 > - Feature X: 7/7 capabilities implemented (complete)

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

@@ -0,0 +1,154 @@
+---
+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
+

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "gspec",
-    "version": "1.16.0",
+    "version": "1.17.1",
     "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,6 +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.
 - **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`.
@@ -30,7 +31,7 @@ If the user explicitly asks you to skip the skill and just do the work, honor th
 
 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]`.
+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.
 
 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