product-spec 0.5.0 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/CHANGELOG.md +16 -0
  2. package/README.md +24 -7
  3. package/assets/claude/commands/product-spec-help.md +84 -0
  4. package/assets/codex/commands/product-spec-help.md +71 -0
  5. package/dist/core/assets/registry.js +1 -0
  6. package/dist/core/assets/registry.js.map +1 -1
  7. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -4,6 +4,22 @@ All notable changes to this project will be documented in this file.
4
4
 
5
5
  ## [Unreleased]
6
6
 
7
+ ## [0.5.1] - 2026-04-11
8
+
9
+ ### Added
10
+
11
+ - New `/product-spec-help` assistant command for both Claude Code and Codex, with overview mode for the full workflow and focused question mode for artifact- or handoff-specific explanations
12
+
13
+ ### Changed
14
+
15
+ - README command listings and workflow guidance now document `/product-spec-help` and the fuller spec-kit handoff chain from `/speckit.specify` through `/speckit.implement`
16
+ - The npm publish workflow now uses GitHub Actions OIDC trusted publishing instead of a long-lived npm publish PAT/token, and the release docs now call out the trusted publisher requirement
17
+
18
+ ### Fixed
19
+
20
+ - Managed asset verification now treats a missing installed `product-spec-help` command like any other drifted assistant asset
21
+ - npm package ignore rules now also exclude `build/` output and `.env.*` files from release artifacts
22
+
7
23
  ## [0.5.0] - 2026-04-03
8
24
 
9
25
  ### Changed
package/README.md CHANGED
@@ -77,6 +77,7 @@ product-spec help
77
77
  After adding an integration, use the installed slash commands inside the assistant:
78
78
 
79
79
  ```text
80
+ /product-spec-help [optional question]
80
81
  /product-spec-domain ...
81
82
  /product-spec-press ...
82
83
  /product-spec-narrative ...
@@ -87,13 +88,15 @@ After adding an integration, use the installed slash commands inside the assista
87
88
 
88
89
  | Target | Command directory | Slash commands |
89
90
  |--------|-------------------|----------------|
90
- | Claude Code | `.claude/commands/` | `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-narrative`, `/product-spec-roadmap`, `/product-spec-align` |
91
- | Codex | `.Codex/commands/` | `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-narrative`, `/product-spec-roadmap`, `/product-spec-align` |
91
+ | Claude Code | `.claude/commands/` | `/product-spec-help`, `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-narrative`, `/product-spec-roadmap`, `/product-spec-align` |
92
+ | Codex | `.Codex/commands/` | `/product-spec-help`, `/product-spec-domain`, `/product-spec-press`, `/product-spec-faq`, `/product-spec-narrative`, `/product-spec-roadmap`, `/product-spec-align` |
92
93
 
93
94
  ## How It Works
94
95
 
95
96
  product-spec creates a `docs/product/` folder in your project that maintains a living view of the product across releases. Primary documents stay focused on the current state of thinking, while companion history documents preserve notable changes over time. Existing projects that still use `product/` or `.product/` are migrated toward `docs/product/` during normal `product-spec add` refreshes when the move is safe.
96
97
 
98
+ Use `/product-spec-help` anytime when you want an overview or a focused explanation of one artifact. It explains the workflow but is not itself a workflow step.
99
+
97
100
  ### Documents
98
101
 
99
102
  | File | Purpose |
@@ -109,8 +112,16 @@ product-spec creates a `docs/product/` folder in your project that maintains a l
109
112
  ### Workflow
110
113
 
111
114
  ```text
112
- /product-spec-domain --> /product-spec-press --> /product-spec-faq --> /product-spec-narrative --> /product-spec-roadmap --> /speckit.specify --> /product-spec-align
113
- (context) (promise) (challenge) (story) (bets) (engineer) (reconcile)
115
+ /product-spec-domain --> /product-spec-press --> /product-spec-faq --> /product-spec-narrative --> /product-spec-roadmap
116
+ (context) (promise) (challenge) (story) (bets)
117
+ |
118
+ v
119
+ /speckit.specify --> /speckit.clarify --> /speckit.plan --> /speckit.tasks --> /speckit.implement
120
+ (scope) (refine) (design) (break down) (build)
121
+ |
122
+ v
123
+ /product-spec-align --> docs/product/current-truth.md
124
+ (reconcile) (current state)
114
125
  ```
115
126
 
116
127
  1. `/product-spec-domain` establishes the domain context: who the users are, what problem matters, and who the alternatives are.
@@ -118,8 +129,9 @@ product-spec creates a `docs/product/` folder in your project that maintains a l
118
129
  3. `/product-spec-faq` challenges the press release with hard questions from customers and stakeholders.
119
130
  4. `/product-spec-narrative` turns the promise and challenge into a durable internal product story.
120
131
  5. `/product-spec-roadmap` sequences future bets and dependencies without replacing current truth.
121
- 6. `/speckit.specify` hands off the next bet to spec-kit for engineering specifications.
122
- 7. `/product-spec-align` reconciles product docs with the evolving engineering scope and maintains `docs/product/current-truth.md`.
132
+ 6. `/speckit.specify` creates the engineering feature specification for the next bet.
133
+ 7. `/speckit.clarify`, `/speckit.plan`, `/speckit.tasks`, and `/speckit.implement` refine that bet into an execution-ready plan and working implementation.
134
+ 8. `/product-spec-align` reconciles product docs with the evolving engineering scope and maintains `docs/product/current-truth.md`.
123
135
 
124
136
  ## Key Concepts
125
137
 
@@ -144,6 +156,11 @@ GitHub Actions now handles:
144
156
  - CI validation on pushes and pull requests
145
157
  - packaging tagged releases
146
158
  - publishing the npm package when a `v*` tag is pushed
159
+ - publishing through npm trusted publishing from GitHub Actions instead of a long-lived PAT/token secret
160
+
161
+ The publish workflow now uses npm trusted publishing from GitHub Actions via OIDC instead of a long-lived `NPM_TOKEN` or PAT-style publish credential. The workflow runs on Node 24 so the bundled npm satisfies trusted publishing requirements, requests `id-token: write`, and publishes with `npm publish` without writing token credentials into `.npmrc`.
162
+
163
+ For public releases published through trusted publishing, npm automatically generates provenance attestations. The npm package must have a trusted publisher configured for this repository and `.github/workflows/publish.yml` before release publishing will succeed.
147
164
 
148
165
  ## Rename Notes
149
166
 
@@ -153,7 +170,7 @@ GitHub Actions now handles:
153
170
 
154
171
  - Node.js and npm
155
172
  - [Claude Code](https://claude.ai/code) and/or Codex for assistant integration targets
156
- - [spec-kit](https://github.com/github/spec-kit) for the `/speckit.specify` portion of the workflow
173
+ - [spec-kit](https://github.com/github/spec-kit) for the `/speckit.specify` through `/speckit.implement` portion of the workflow
157
174
 
158
175
  ## Changelog
159
176
 
package/assets/claude/commands/product-spec-help.md ADDED
@@ -0,0 +1,84 @@
1
+ ---
2
+ description: Explain the product-spec workflow and answer questions about steps, artifacts, and handoffs.
3
+ handoffs:
4
+ - label: Start with Domain
5
+ agent: product-spec-domain
6
+ prompt: Help me capture the domain context for this project
7
+ - label: Write the Next Spec
8
+ agent: speckit.specify
9
+ prompt: Create a technical spec for the next roadmap bet. I want to build...
10
+ ---
11
+
12
+ ## User Input
13
+
14
+ ```text
15
+ $ARGUMENTS
16
+ ```
17
+
18
+ You **MUST** consider the user input before proceeding (if not empty).
19
+
20
+ ## Outline
21
+
22
+ You are explaining how `product-spec` and `spec-kit` fit together. `/product-spec-help` does **not** create or update a managed product artifact of its own. Its job is to explain the workflow clearly, answer focused questions, and point the user to the right next step.
23
+
24
+ ### Canonical Workflow Reference
25
+
26
+ Use this workflow as the primary source of truth, even if the current project has not created these files yet:
27
+
28
+ | Step | Usually Needs | Creates or Updates | Why It Matters |
29
+ |------|---------------|-------------------|----------------|
30
+ | `/product-spec-domain` | A project idea, market context, or customer problem | `docs/product/domain.md` | Defines the users, problem space, terminology, and competitive context that the rest of the product work builds on. |
31
+ | `/product-spec-press` | Usually `docs/product/domain.md` | `docs/product/press.md` | Turns the product idea into a customer-facing promise written as if it already shipped. |
32
+ | `/product-spec-faq` | Usually `docs/product/press.md` | `docs/product/faq.md` | Pressure-tests the promise with hard customer and stakeholder questions before engineering commits to it. |
33
+ | `/product-spec-narrative` | Usually `docs/product/domain.md`, `docs/product/press.md`, and `docs/product/faq.md` | `docs/product/narrative.md` | Synthesizes the context, promise, and objections into a durable internal product story. |
34
+ | `/product-spec-roadmap` | Usually `docs/product/narrative.md` | `docs/product/roadmap.md` | Turns the durable story into sequenced future bets without confusing future intent with current truth. |
35
+ | `/speckit.specify` | Usually a scoped roadmap bet or clearly defined next feature | `specs/<feature>/spec.md` | Converts the next bet into an engineering-ready feature specification. |
36
+ | `/speckit.clarify` | Usually `specs/<feature>/spec.md` | Updates `specs/<feature>/spec.md` | Resolves important scope, UX, or security uncertainties without inventing a new primary artifact. |
37
+ | `/speckit.plan` | `specs/<feature>/spec.md` | `specs/<feature>/plan.md` | Turns the approved feature specification into a technical implementation plan. |
38
+ | `/speckit.tasks` | `specs/<feature>/plan.md` | `specs/<feature>/tasks.md` | Breaks the plan into an ordered implementation checklist. |
39
+ | `/speckit.implement` | `specs/<feature>/tasks.md` | Updates source code and project files | Executes the task plan and turns the spec into working changes. |
40
+ | `/product-spec-align` | Updated specs, implementation changes, or newly shipped reality | `docs/product/current-truth.md` and related product docs | Reconciles product language with what is actually true in the product today. |
41
+
42
+ ### Response Mode Selection
43
+
44
+ 1. **If the user input is empty or whitespace only, use overview mode**:
45
+ - Start with a one-sentence framing that `/product-spec-help` explains the workflow but is not itself a production step.
46
+ - Show a compact workflow diagram such as:
47
+
48
+ ```text
49
+ /product-spec-domain -> /product-spec-press -> /product-spec-faq -> /product-spec-narrative -> /product-spec-roadmap
50
+ |
51
+ v
52
+ /speckit.specify -> /speckit.plan -> /speckit.tasks -> /speckit.implement
53
+ |
54
+ v
55
+ /product-spec-align -> docs/product/current-truth.md
56
+ ```
57
+
58
+ - After the diagram, include a scan-friendly table or bullets that keep the same four ideas visible for each step:
59
+ - what usually comes before it
60
+ - what it creates or updates
61
+ - what the artifact is
62
+ - why that artifact matters
63
+ - Keep the answer compact enough that a first-time user can understand the flow in under a minute.
64
+
65
+ 2. **If the user input is not empty, use question mode**:
66
+ - Answer the question directly first in plain language.
67
+ - Then add focused workflow context using a compact structure such as:
68
+ - `Usually needs: ...`
69
+ - `Creates/updates: ...`
70
+ - `Why it matters: ...`
71
+ - `Next: ...`
72
+ - Only include the surrounding steps needed to make the answer clear. Do **not** dump the whole workflow unless it helps answer the question.
73
+ - Treat prompts like `what is domain.md and why is it needed?` and `what comes after roadmap?` as representative examples of the level of detail the user wants.
74
+
75
+ ### Answering Rules
76
+
77
+ 1. Use canonical product artifact paths under `docs/product/`.
78
+ 2. If the user mentions a legacy path such as `product/domain.md` or `.product/domain.md`, explain that the canonical location now lives under `docs/product/` and treat the older path as legacy migration context.
79
+ 3. If the user asks about an ambiguous or unknown term, make the best reasonable mapping to the closest canonical concept and say what you are assuming.
80
+ 4. If the user asks about `roadmap.md` versus `current-truth.md`, make the distinction explicit:
81
+ - `roadmap.md` is future-facing and sequences bets
82
+ - `current-truth.md` describes what is actually true in the product today
83
+ 5. If the user asks about a refinement or execution step such as `/speckit.clarify` or `/speckit.implement`, be explicit that those steps usually update an existing artifact or the codebase rather than creating a new primary planning document.
84
+ 6. Suggest the next logical workflow step when it naturally follows from the answer.
package/assets/codex/commands/product-spec-help.md ADDED
@@ -0,0 +1,71 @@
1
+ ---
2
+ description: Explain the product-spec workflow and answer questions about steps, artifacts, and handoffs.
3
+ handoffs:
4
+ - label: Start with Domain
5
+ agent: product-spec-domain
6
+ prompt: Help me capture the domain context for this project
7
+ - label: Write the Next Spec
8
+ agent: speckit.specify
9
+ prompt: Create a technical spec for the next roadmap bet. I want to build...
10
+ ---
11
+
12
+ ## User Input
13
+
14
+ ```text
15
+ $ARGUMENTS
16
+ ```
17
+
18
+ You **MUST** consider the user input before proceeding (if not empty).
19
+
20
+ ## Outline
21
+
22
+ You are explaining how `product-spec` and `spec-kit` fit together. `/product-spec-help` never creates a managed product artifact. It explains the workflow, answers focused questions, and helps the user find the right next step.
23
+
24
+ ### Canonical Workflow Reference
25
+
26
+ Use this workflow as the default source of truth:
27
+
28
+ | Step | Usually Needs | Creates or Updates | Why It Matters |
29
+ |------|---------------|-------------------|----------------|
30
+ | `/product-spec-domain` | A project idea, market context, or customer problem | `docs/product/domain.md` | Defines the users, problem space, terminology, and competitive context. |
31
+ | `/product-spec-press` | Usually `docs/product/domain.md` | `docs/product/press.md` | Turns the idea into a customer-facing promise. |
32
+ | `/product-spec-faq` | Usually `docs/product/press.md` | `docs/product/faq.md` | Challenges the promise before engineering commits to it. |
33
+ | `/product-spec-narrative` | Usually `docs/product/domain.md`, `docs/product/press.md`, and `docs/product/faq.md` | `docs/product/narrative.md` | Creates the durable internal product story. |
34
+ | `/product-spec-roadmap` | Usually `docs/product/narrative.md` | `docs/product/roadmap.md` | Sequences future bets without replacing current truth. |
35
+ | `/speckit.specify` | Usually a scoped roadmap bet or clearly defined next feature | `specs/<feature>/spec.md` | Creates the engineering-ready feature specification. |
36
+ | `/speckit.clarify` | Usually `specs/<feature>/spec.md` | Updates `specs/<feature>/spec.md` | Resolves important open questions without inventing a new primary artifact. |
37
+ | `/speckit.plan` | `specs/<feature>/spec.md` | `specs/<feature>/plan.md` | Turns the spec into a technical implementation plan. |
38
+ | `/speckit.tasks` | `specs/<feature>/plan.md` | `specs/<feature>/tasks.md` | Breaks the plan into an execution checklist. |
39
+ | `/speckit.implement` | `specs/<feature>/tasks.md` | Updates source code and project files | Executes the plan and produces working changes. |
40
+ | `/product-spec-align` | Updated specs, implementation changes, or newly shipped reality | `docs/product/current-truth.md` and related product docs | Reconciles product language with what is actually true today. |
41
+
42
+ ### Response Modes
43
+
44
+ 1. **Overview mode**: if the user input is empty or whitespace only.
45
+ - Start with a one-sentence framing that `/product-spec-help` explains the workflow but is not itself a production step.
46
+ - Show a compact workflow diagram.
47
+ - Follow with a scan-friendly table or bullets covering:
48
+ - what usually comes before each step
49
+ - what it creates or updates
50
+ - what the artifact is
51
+ - why it matters
52
+ - Keep the answer compact enough to scan quickly.
53
+
54
+ 2. **Question mode**: if the user input is not empty.
55
+ - Answer the question directly first.
56
+ - Then add focused context:
57
+ - `Usually needs: ...`
58
+ - `Creates/updates: ...`
59
+ - `Why it matters: ...`
60
+ - `Next: ...`
61
+ - Only include the surrounding workflow needed to make the answer clear.
62
+ - Treat prompts like `what is domain.md and why is it needed?` and `what comes after roadmap?` as representative examples of the depth the user wants.
63
+
64
+ ### Answering Rules
65
+
66
+ 1. Use canonical product artifact paths under `docs/product/`.
67
+ 2. If the user mentions `product/` or `.product/`, explain that those are legacy paths and normalize to `docs/product/`.
68
+ 3. If the user asks about an unknown or ambiguous term, make the best reasonable mapping to the closest canonical concept and say what you are assuming.
69
+ 4. If the user asks about `roadmap.md` and `current-truth.md`, be explicit that roadmap is future-facing and current truth describes what is true today.
70
+ 5. If the user asks about `/speckit.clarify` or `/speckit.implement`, explain that those usually update an existing artifact or the codebase rather than creating a new primary planning document.
71
+ 6. Suggest the next logical step when it naturally follows from the answer.
package/dist/core/assets/registry.js CHANGED
@@ -5,6 +5,7 @@ export const PRODUCT_TEMPLATES_DIR = `${PRODUCT_DOCS_DIR}/templates`;
5
5
  export const PREVIOUS_PRODUCT_TEMPLATES_DIR = `${PREVIOUS_PRODUCT_DOCS_DIR}/templates`;
6
6
  export const LEGACY_PRODUCT_TEMPLATES_DIR = `${LEGACY_PRODUCT_DOCS_DIR}/templates`;
7
7
  const assistantCommands = [
8
+ "product-spec-help.md",
8
9
  "product-spec-domain.md",
9
10
  "product-spec-press.md",
10
11
  "product-spec-faq.md",
package/dist/core/assets/registry.js.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"registry.js","sourceRoot":"","sources":["../../../src/core/assets/registry.ts"],"names":[],"mappings":"AAEA,MAAM,CAAC,MAAM,gBAAgB,GAAG,cAAc,CAAC;AAC/C,MAAM,CAAC,MAAM,yBAAyB,GAAG,SAAS,CAAC;AACnD,MAAM,CAAC,MAAM,uBAAuB,GAAG,UAAU,CAAC;AAClD,MAAM,CAAC,MAAM,qBAAqB,GAAG,GAAG,gBAAgB,YAAY,CAAC;AACrE,MAAM,CAAC,MAAM,8BAA8B,GAAG,GAAG,yBAAyB,YAAY,CAAC;AACvF,MAAM,CAAC,MAAM,4BAA4B,GAAG,GAAG,uBAAuB,YAAY,CAAC;AAUnF,MAAM,iBAAiB,GAAG;IACxB,wBAAwB;IACxB,uBAAuB;IACvB,qBAAqB;IACrB,2BAA2B;IAC3B,yBAAyB;IACzB,uBAAuB;CACxB,CAAC;AAEF,MAAM,eAAe,GAAG;IACtB,oBAAoB;IACpB,mBAAmB;IACnB,iBAAiB;IACjB,uBAAuB;IACvB,qBAAqB;IACrB,2BAA2B;CAC5B,CAAC;AAEF,MAAM,gBAAgB,GAAG;IACvB,4BAA4B;IAC5B,2BAA2B;IAC3B,yBAAyB;IACzB,+BAA+B;IAC/B,6BAA6B;IAC7B,mCAAmC;CACpC,CAAC;AAEF,SAAS,oBAAoB,CAAC,MAAuB,EAAE,UAAkB;IACvE,OAAO,iBAAiB,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC;QAC1C,EAAE,EAAE,GAAG,MAAM,IAAI,QAAQ,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,EAAE;QAChD,QAAQ,EAAE,mBAAmB;QAC7B,MAAM;QACN,UAAU,EAAE,UAAU,MAAM,aAAa,QAAQ,EAAE;QACnD,UAAU,EAAE,GAAG,UAAU,IAAI,QAAQ,EAAE;KACxC,CAAC,CAAC,CAAC;AACN,CAAC;AAED,SAAS,iBAAiB;IACxB,MAAM,aAAa,GAAG,eAAe,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,gBAAgB,CAAC,QAAQ,EAAE,kBAAkB,CAAC,CAAC,CAAC;IACxG,MAAM,aAAa,GAAG,gBAAgB,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CACtD,gBAAgB,CAAC,QAAQ,EAAE,0BAA0B,EAAE,SAAS,CAAC,CAClE,CAAC;IAEF,OAAO,CAAC,GAAG,aAAa,EAAE,GAAG,aAAa,CAAC,CAAC;AAC9C,CAAC;AAED,SAAS,gBAAgB,CACvB,QAAgB,EAChB,QAAuB,EACvB,MAAe;IAEf,MAAM,WAAW,GAAG,MAAM,CAAC,CAAC,CAAC,4BAA4B,MAAM,EAAE,CAAC,CAAC,CAAC,0BAA0B,CAAC;IAC/F,MAAM,SAAS,GAAG,MAAM,CAAC,CAAC,CAAC,GAAG,qBAAqB,IAAI,MAAM,EAAE,CAAC,CAAC,CAAC,qBAAqB,CAAC;IAExF,OAAO;QACL,EAAE,EAAE,UAAU,QAAQ,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,EAAE;QAC7C,QAAQ;QACR,MAAM,EAAE,QAAQ;QAChB,UAAU,EAAE,GAAG,WAAW,IAAI,QAAQ,EAAE;QACxC,UAAU,EAAE,GAAG,SAAS,IAAI,QAAQ,EAAE;KACvC,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,sBAAsB,GAA+C;IAChF,MAAM,EAAE,oBAAoB,CAAC,QAAQ,EAAE,kBAAkB,CAAC;IAC1D,KAAK,EAAE,oBAAoB,CAAC,OAAO,EAAE,iBAAiB,CAAC;CACxD,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG,iBAAiB,EAAE,CAAC;AAEvD,MAAM,UAAU,yBAAyB,CAAC,MAAuB;IAC/D,OAAO,sBAAsB,CAAC,MAAM,CAAC,CAAC;AACxC,CAAC"}
1
+ {"version":3,"file":"registry.js","sourceRoot":"","sources":["../../../src/core/assets/registry.ts"],"names":[],"mappings":"AAEA,MAAM,CAAC,MAAM,gBAAgB,GAAG,cAAc,CAAC;AAC/C,MAAM,CAAC,MAAM,yBAAyB,GAAG,SAAS,CAAC;AACnD,MAAM,CAAC,MAAM,uBAAuB,GAAG,UAAU,CAAC;AAClD,MAAM,CAAC,MAAM,qBAAqB,GAAG,GAAG,gBAAgB,YAAY,CAAC;AACrE,MAAM,CAAC,MAAM,8BAA8B,GAAG,GAAG,yBAAyB,YAAY,CAAC;AACvF,MAAM,CAAC,MAAM,4BAA4B,GAAG,GAAG,uBAAuB,YAAY,CAAC;AAUnF,MAAM,iBAAiB,GAAG;IACxB,sBAAsB;IACtB,wBAAwB;IACxB,uBAAuB;IACvB,qBAAqB;IACrB,2BAA2B;IAC3B,yBAAyB;IACzB,uBAAuB;CACxB,CAAC;AAEF,MAAM,eAAe,GAAG;IACtB,oBAAoB;IACpB,mBAAmB;IACnB,iBAAiB;IACjB,uBAAuB;IACvB,qBAAqB;IACrB,2BAA2B;CAC5B,CAAC;AAEF,MAAM,gBAAgB,GAAG;IACvB,4BAA4B;IAC5B,2BAA2B;IAC3B,yBAAyB;IACzB,+BAA+B;IAC/B,6BAA6B;IAC7B,mCAAmC;CACpC,CAAC;AAEF,SAAS,oBAAoB,CAAC,MAAuB,EAAE,UAAkB;IACvE,OAAO,iBAAiB,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC;QAC1C,EAAE,EAAE,GAAG,MAAM,IAAI,QAAQ,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,EAAE;QAChD,QAAQ,EAAE,mBAAmB;QAC7B,MAAM;QACN,UAAU,EAAE,UAAU,MAAM,aAAa,QAAQ,EAAE;QACnD,UAAU,EAAE,GAAG,UAAU,IAAI,QAAQ,EAAE;KACxC,CAAC,CAAC,CAAC;AACN,CAAC;AAED,SAAS,iBAAiB;IACxB,MAAM,aAAa,GAAG,eAAe,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,gBAAgB,CAAC,QAAQ,EAAE,kBAAkB,CAAC,CAAC,CAAC;IACxG,MAAM,aAAa,GAAG,gBAAgB,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CACtD,gBAAgB,CAAC,QAAQ,EAAE,0BAA0B,EAAE,SAAS,CAAC,CAClE,CAAC;IAEF,OAAO,CAAC,GAAG,aAAa,EAAE,GAAG,aAAa,CAAC,CAAC;AAC9C,CAAC;AAED,SAAS,gBAAgB,CACvB,QAAgB,EAChB,QAAuB,EACvB,MAAe;IAEf,MAAM,WAAW,GAAG,MAAM,CAAC,CAAC,CAAC,4BAA4B,MAAM,EAAE,CAAC,CAAC,CAAC,0BAA0B,CAAC;IAC/F,MAAM,SAAS,GAAG,MAAM,CAAC,CAAC,CAAC,GAAG,qBAAqB,IAAI,MAAM,EAAE,CAAC,CAAC,CAAC,qBAAqB,CAAC;IAExF,OAAO;QACL,EAAE,EAAE,UAAU,QAAQ,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,EAAE;QAC7C,QAAQ;QACR,MAAM,EAAE,QAAQ;QAChB,UAAU,EAAE,GAAG,WAAW,IAAI,QAAQ,EAAE;QACxC,UAAU,EAAE,GAAG,SAAS,IAAI,QAAQ,EAAE;KACvC,CAAC;AACJ,CAAC;AAED,MAAM,CAAC,MAAM,sBAAsB,GAA+C;IAChF,MAAM,EAAE,oBAAoB,CAAC,QAAQ,EAAE,kBAAkB,CAAC;IAC1D,KAAK,EAAE,oBAAoB,CAAC,OAAO,EAAE,iBAAiB,CAAC;CACxD,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG,iBAAiB,EAAE,CAAC;AAEvD,MAAM,UAAU,yBAAyB,CAAC,MAAuB;IAC/D,OAAO,sBAAsB,CAAC,MAAM,CAAC,CAAC;AACxC,CAAC"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "product-spec",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "product-spec CLI for installing product-management command assets into Claude Code and Codex projects",
5
5
  "license": "MIT",
6
6
  "repository": {