@boopkit/cap-product-design 0.6.8 → 0.6.9

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 (3) hide show
  1. package/package.json +1 -1
  2. package/skills/boop-product-design-thought-partnership/SKILL.md +1 -1
  3. package/skills/boop-writing-semantic-line-breaks/SKILL.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@boopkit/cap-product-design",
3
- "version": "0.6.8",
3
+ "version": "0.6.9",
4
4
  "description": "Product design skills for AI agents",
5
5
  "files": [
6
6
  "skills/",
package/skills/boop-product-design-thought-partnership/SKILL.md CHANGED
@@ -76,4 +76,4 @@ When the user opens a design conversation:
76
76
  - [`boop-product-design-feature-requirements`](../boop-product-design-feature-requirements/SKILL.md) — the artifact-shape skill for feature reqs (jobs-to-be-done framing, stance, non-goals). This skill is about the *conversation* that produces a feature reqs doc; that skill is about what the doc itself looks like.
77
77
  - [`boop-product-design-engineering-design`](../boop-product-design-engineering-design/SKILL.md) — the artifact-shape skill for engineering design docs. Same relationship.
78
78
  - [`boop-writing-technical-prose`](../boop-writing-technical-prose/SKILL.md) — apply when capturing the conversation into any artifact. Specs drift into shorthand as easily as anything else.
79
- - [`boop-project-mgmt-beads-planning`](../../../cap-project-mgmt/skills/boop-project-mgmt-beads-planning/SKILL.md) — when the conversation produces a bd issue, the issue body should follow the goal/approach/context shape described there for non-trivial work. The same hypothesis-not-commitment discipline applies to issue bodies as it does to spec prose.
79
+ - `boop-project-mgmt-beads-planning` — when the conversation produces a bd issue, the issue body should follow the goal/approach/context shape described there for non-trivial work. The same hypothesis-not-commitment discipline applies to issue bodies as it does to spec prose.
package/skills/boop-writing-semantic-line-breaks/SKILL.md CHANGED
@@ -93,7 +93,7 @@ A line carrying a long markdown link is shorter than it looks; judge it by what
93
93
  Write issue bodies as paragraphs separated by blank lines.
94
94
  - **Chat responses.** Nothing is being diffed. Write normally.
95
95
  - **Code and inline comments.** Follow the surrounding code's conventions.
96
- - **Commit messages.** The subject and body conventions in [`boop-coding-commit-changes`](../../../cap-coding/skills/boop-coding-commit-changes/SKILL.md) already govern these.
96
+ - **Commit messages.** The subject and body conventions in `boop-coding-commit-changes` already govern these.
97
97
 
98
98
  ## Editing a file that is not yet broken this way
99
99