@boopkit/cap-product-design 0.1.1 → 0.3.0

package/README.md

@@ -0,0 +1,49 @@
+# @boopkit/cap-product-design
+
+**Part of [Boop](https://www.npmjs.com/package/@boopkit/cli)** — a bootstrap platform for AI-first builders. `boop init` scaffolds a running Node/TypeScript web app from composable **capabilities**, each one bundling the code, dependencies, middleware wiring, and agent skills needed for a feature. You pick the capabilities; `boop add` handles the rest.
+
+`cap-product-design` is a skills-only capability covering the "think before you build" stretch of the workflow. It teaches an agent how to pull clear requirements from a vague founder brief, how to write an engineering design doc that exposes trade-offs (not just outcomes), how to document a feature for a specific audience, and how to fold new knowledge into the project's living `reference/` wiki after shipping.
+
+## What You Get
+
+A bundle of agent-facing skill files for requirements, design, feature docs, and reference-doc integration. No runtime code, no dependencies, no server wiring — documentation-as-code for the agents working in your repo.
+
+### Skills installed
+
+Copied into `skills/` on install:
+
+- `reqs.feature-requirements.skill.md` — how to turn a brief or vague directive into real requirements: ask 3-5 focused trade-off questions, push back on ambiguity without interrogating, and know when enough clarity is enough to proceed.
+- `reqs.feature-documentation.skill.md` — how to write feature documentation aimed at a specific audience and activity, with the right tone and grounding for readers who haven't done this before.
+- `design.engineering-design.skill.md` — the engineering design doc structure (Goals, Non-Goals, Approach, Alternatives, Tradeoffs, Open Questions) with a stance: make the *decision* visible, not just the solution.
+- `docs.reference-integration.skill.md` — how to blend new knowledge into `reference/` after a feature lands, keeping it a living wiki of what the system actually is, not a pile of per-feature pages.
+
+## Requirements
+
+**Other capabilities:** none.
+
+**npm dependencies added to your project:** none. `cap-product-design` is pure documentation for agents.
+
+**Environment variables:** none.
+
+**Project files referenced:** several skills point at `reference/tenets.ref.md` for overarching principles. That file is provided by the `web-app` profile's `reference/` directory. In other profiles, the skill will still work — the reference link just won't resolve.
+
+## Usage
+
+Skills are meant to be read by AI agents, not humans (though humans are welcome). Once installed they live in your project's `skills/` directory alongside skills from other capabilities.
+
+How agents find them depends on the harness:
+
+- Projects with a Claude Code `CLAUDE.md` typically instruct the agent to consult `skills/index.md` or the relevant `.skill.md` file before acting.
+- Harnesses with a native skill-discovery system (e.g. slash-command style skills) surface them by filename.
+
+A typical flow: a founder gives the agent a two-sentence feature brief. The agent reads `reqs.feature-requirements.skill.md` and asks a few trade-off questions to fill the gaps. Once the shape is clear it reads `design.engineering-design.skill.md` and writes a design doc with an explicit Alternatives section. After the feature ships, it reads `docs.reference-integration.skill.md` and blends the new behaviour into the existing concept pages in `reference/` — not a new feature-specific page.
+
+## Added by
+
+Included by default in the `web-app` profile.
+
+Add to an existing project with:
+
+```bash
+boop add product-design
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cap-product-design",
-  "version": "0.1.1",
+  "version": "0.3.0",
   "description": "Product design skills for AI agents",
   "files": [
     "skills/",