@boopkit/cli 0.6.7 → 0.6.8

package/README.md

@@ -73,7 +73,7 @@ A profile is where a project starts. Today there's one; more will follow as the
 
 Full-stack web application — Express + Handlebars + Tailwind CSS + PostgreSQL via Prisma, deployable to Heroku.
 
-Ships with application capabilities (`web`, `api`, `services`, `database`), development skills (`coding`, `testing`, `project-mgmt`, `product-design`, `skills`), and the `hello` demo capability.
+Ships with application capabilities (`web`, `api`, `services`, `database`), development skills (`coding`, `testing`, `project-mgmt`, `product-design`, `skills`, `workflows`), and the `hello` demo capability.
 
 List profiles with `boop list profiles`.
 
@@ -105,6 +105,7 @@ Pick what the product needs. `boop add <name>` handles the wiring — npm depend
 | `product-design` | Product design skills — feature requirements, engineering design, documentation, design thought-partnership, and technical prose |
 | `ux` | UX judgement (purpose + visual) and the app-UI evaluation and delivery workflows |
 | `skills` | Skill-authoring and skill-discovery guidance for extending the skill library |
+| `workflows` | Reusable end-to-end dev/writing workflows — feature, light, refactor, test-audit, architecture-audit, issue-sweep, website, design-handoff, knowledge-backfill |
 
 ### Skills each capability ships
 
@@ -116,11 +117,12 @@ Adding a capability installs its skills into your project's `skills/` directory.
 **Development capabilities (skills only — no runtime code)**
 
 - **`coding`** — boop-coding-beads-flow, boop-coding-development, boop-coding-commit-changes, boop-coding-review-changes, boop-coding-debugging
-- **`product-design`** — boop-product-design-engineering-design, boop-product-design-feature-documentation, boop-product-design-feature-requirements, boop-product-design-reference-integration, boop-product-design-thought-partnership, boop-writing-technical-prose
+- **`product-design`** — boop-product-design-engineering-design, boop-product-design-feature-documentation, boop-product-design-feature-requirements, boop-product-design-reference-integration, boop-product-design-thought-partnership, boop-writing-technical-prose, boop-writing-documents
 - **`project-mgmt`** — boop-project-mgmt-beads-planning, boop-project-mgmt-engineering-planning
-- **`skills`** — boop-skill-authoring, boop-skills-discovery, boop-skills-agent-surface-design
+- **`skills`** — boop-skill-authoring, boop-skills-discovery, boop-skills-agent-surface-design, boop-get-smart, boop-so-what
 - **`testing`** — boop-testing-tdd-light, boop-testing-testing-express-web, boop-testing-testing
 - **`ux`** — boop-ux-purpose-judgement, boop-ux-visual-judgement, boop-ux-eval-and-refine-workflow, boop-ux-app-ui-dev-workflow
+- **`workflows`** — boop-feature-dev-workflow, boop-light-dev-workflow, boop-refactor-dev-workflow, boop-test-audit-workflow, boop-architecture-audit-workflow, boop-issue-sweep-workflow, boop-website-dev-workflow, boop-design-handoff-workflow, boop-knowledge-backfill
 
 **Application capabilities**
 

package/dist/capability-catalog.json

@@ -124,5 +124,12 @@
     "type": "application",
     "package": "@boopkit/cap-web",
     "requires": []
+  },
+  {
+    "name": "workflows",
+    "description": "Reusable end-to-end development and writing workflows",
+    "type": "development",
+    "package": "@boopkit/cap-workflows",
+    "requires": []
   }
 ]

package/dist/capability-versions.json

@@ -7,13 +7,14 @@
   "@boopkit/cap-email": "0.4.2",
   "@boopkit/cap-hello": "0.4.0",
   "@boopkit/cap-noticeboard": "0.4.0",
-  "@boopkit/cap-product-design": "0.6.4",
+  "@boopkit/cap-product-design": "0.6.5",
   "@boopkit/cap-project-mgmt": "0.4.4",
   "@boopkit/cap-services": "0.4.2",
-  "@boopkit/cap-skills": "0.5.1",
-  "@boopkit/cap-testing": "0.5.1",
+  "@boopkit/cap-skills": "0.5.2",
+  "@boopkit/cap-testing": "0.5.2",
   "@boopkit/cap-users": "0.4.3",
   "@boopkit/cap-ux": "0.2.2",
   "@boopkit/cap-web": "0.5.2",
+  "@boopkit/cap-workflows": "0.1.0",
   "@boopkit/logger": "0.4.0"
 }

package/docs/skills.md

@@ -22,6 +22,7 @@ Every capability ships **agent skills** — focused `SKILL.md` guides that `boop
 - **boop-product-design-reference-integration** — When you need to integrate new knowledge into the project's `reference/` directory after completing a feature, fixing a bug that changes behavior, or adding a capability.
 - **boop-product-design-thought-partnership** — When the user wants to think out loud through a design — a feature, a capability, a strategic direction — be a thought partner, not an implementer: hold the conversation at user-and-value altitude, honor uncertainty with hypotheses rather than pretend-decisions, and keep software-shaped concerns downstream of the user's lived problems.
 - **boop-writing-technical-prose** — When writing chat responses, summaries, bd issue bodies, specifications, specs, or any artifact a fresh reader will pick up cold, write grammatical conversational English. Avoid the agent-shorthand patterns that compress meaning at the cost of legibility.
+- **boop-writing-documents** — When you need to write a document someone will read cold and act on — a proposal, strategy memo, analysis, recommendation, or status write-up — and want the discipline of the Amazon six-pager: narrative prose, a declared length budget, claims that carry their evidence, and the hard questions answered inside the document.
 
 ### `project-mgmt` — Project management with beads
 
@@ -33,6 +34,8 @@ Every capability ships **agent skills** — focused `SKILL.md` guides that `boop
 - **boop-skill-authoring** — When you need to add or update an agent skill in this project, follow this format and checklist.
 - **boop-skills-discovery** — When you pick up a non-trivial task, sweep the available skills for ones relevant to the work before you start, as a backstop for an issue that missed a breadcrumb.
 - **boop-skills-agent-surface-design** — When you design or audit tool surfaces (tools, schemas, APIs, conventions) that LLM agents will reach for, decide where to put the friction — adapt the system to the agent, or make the existing thing more discoverable. Last resort: prompt-engineer.
+- **boop-get-smart** — When there is a recurring fault in your own behaviour during a chat, run the five whys to find its root cause, and agree a change with the operator that makes it less likely.
+- **boop-so-what** — When the operator asks for the so-what, or says some version of 'thanks for the essay', compress what you just produced into three sentences about what they should care about.
 
 ### `testing` — Jest testing setup
 
@@ -47,6 +50,18 @@ Every capability ships **agent skills** — focused `SKILL.md` guides that `boop
 - **boop-ux-eval-and-refine-workflow** — When you are tasked with iteratively evaluating and improving an existing rendered page (discovery, not delivery), follow this workflow. Inner loop: capture → eval → recommend → implement → re-capture. Outer: knowledge integration.
 - **boop-ux-app-ui-dev-workflow** — When you are tasked with improving an existing app-side page (app UX, not marketing) end-to-end and the input is a target page rather than a written spec, follow this beads-issue-per-step workflow. Sibling to feature-dev-workflow but stripped of backend phases. The judgement lenses are the planning input.
 
+### `workflows` — Reusable end-to-end development and writing workflows
+
+- **boop-feature-dev-workflow** — When you are tasked with building a feature end-to-end, follow this guidance.
+- **boop-light-dev-workflow** — When you are extending an existing system (front-end, back-end, or full-stack) toward a goal — wiring something new from data and patterns that already exist, not building greenfield — follow this grounded flow: goal → investigate the real system → design → critique → decompose into one scoped epic + child issues → run them → close out. Loop-drivable via boop loop --work --flow; lighter than feature-dev-workflow.
+- **boop-refactor-dev-workflow** — When you need to change a contract, cardinality, or shape that existing code already depends on — usually to make a feature buildable — follow this workflow instead of the feature workflow.
+- **boop-test-audit-workflow** — Use when a set of tests is not testing the purpose of the code: mocks that verify data the test itself fed in, tests that exercise the platform rather than our code, or a stubbed seam where the integration is the actual risk. Also use when tests are so coupled to the shape of the implementation that they check a label, an exact string, or a call sequence rather than a behaviour. This workflow removes tests that cannot go red for a real reason, rewrites the ones that check a real goal at the wrong level, merges duplicates, and does not lose coverage. It explicitly does not target good tests merely because a coming change will make them need updating. The sibling of light-dev-workflow for reworking tests rather than building features.
+- **boop-architecture-audit-workflow** — When you need to judge whether an area of shipped code is structurally healthy and decide what is worth fixing — undesired coupling, concerns bleeding across layers or domain boundaries, interfaces that are not composable because they are use-case specific or unparameterized — follow this process: scope one area and name the properties it should uphold → check the tests can catch you → measure before reading → grade every property and classify every finding against a named change → critique → operator gate → decompose → execute via refactor-dev-workflow. The sibling of test-audit-workflow for production code rather than tests. Not for finding bugs, and not for executing a structural change you have already decided on.
+- **boop-issue-sweep-workflow** — When the bd queue has accumulated a noisy backlog of lingering P1/P2 items — paper-cuts, small refactors, dead code, cosmetic bugs, taxonomy drift — and you want to clear them autonomously in a sequence that supports the week's goals, follow this process: inventory → cluster by theme → pick a cluster with the operator → run autonomously in one sweep worktree → hand off for a single UAT pass → log. The work lands in a worktree for one operator review rather than on main; it arrives with no decisions left in it.
+- **boop-website-dev-workflow** — When you are tasked with implementing website changes end-to-end (new pages, page rewrites, IA changes, content/CTA updates), follow this guidance.
+- **boop-design-handoff-workflow** — When the operator hands off a design package (a README plus a drop-in view template and CSS) for a redesigned surface, follow this process: read the README, VERIFY its claims against the real code, surface any buried decision to the operator, file an issue, run it as a sub-agent (branch for UAT or merge-on-clean-visual-check), then close out with knowledge integration and archival. The README is confident; confidence is not correctness — verify before you run.
+- **boop-knowledge-backfill** — When you need to integrate new knowledge from a set of specs or completed work that was not documented in reference at the time it shipped. This often happens when a feature is developed under a tight deadline and the team prioritizes shipping over documentation, or when work was done before the reference system was fully established.
+
 ## Application capabilities
 
 ### `api` — REST API with Express
@@ -85,4 +100,4 @@ Every capability ships **agent skills** — focused `SKILL.md` guides that `boop
 
 ---
 
-Standalone workflow skills (e.g. `boop-feature-dev-workflow`, `boop-light-dev-workflow`, `boop-issue-sweep-workflow`, `boop-design-handoff-workflow`) live in the repo's top-level `skills/` directory rather than in a capability package, so they are not listed above.
+Boop-maintainer skills (e.g. `boop-capability-development`, `boop-downstream-harvest`, `boop-loop-conductor`, `boop-dolt-recovery`) live in the repo's top-level `skills/` directory rather than in a capability package, so they do not ship and are not listed above.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cli",
-  "version": "0.6.7",
+  "version": "0.6.8",
   "description": "boop: the opinionated bootstrap for founder friendly, AI-first web apps - code plus agent skills, composable from day one.",
   "main": "dist/cli.js",
   "workspaces": [

package/profiles/web-app/profile.md

@@ -13,6 +13,7 @@ defaultCapabilities:
   - project-mgmt
   - product-design
   - skills
+  - workflows
   # Demo
   - hello
 kernel: