@boopkit/cap-workflows 0.2.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cap-workflows",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Reusable end-to-end development and writing workflows for AI agents",
   "files": [
     "skills/",

package/skills/boop-architecture-audit-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "When you need to judge whether an area of shipped code is structur
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Architecture audit workflow — judge an area's structural health, and find the debt a named change would actually hit.
 

package/skills/boop-design-handoff-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "When the operator hands off a design package (a README plus a drop
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Design-handoff workflow — turn a design package into shipped, reviewed code.
 

package/skills/boop-feature-dev-workflow/SKILL.md

@@ -4,6 +4,11 @@ description: "When you are tasked with building a feature end-to-end, follow thi
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Workflow for building features.
 When you are tasked with building a feature end-to-end, follow this guidance.
 

package/skills/boop-issue-sweep-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "When the bd queue has accumulated a noisy backlog of lingering P1/
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Issue sweep workflow — clear lingering backlog noise without spending the operator's judgment.
 

package/skills/boop-knowledge-backfill/SKILL.md

@@ -4,6 +4,11 @@ description: "When you need to integrate new knowledge from a set of specs or co
 metadata:
   category: docs
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Knowledge Backfill
 
    **a. Integrate into reference:**

package/skills/boop-light-dev-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "When you are extending an existing system (front-end, back-end, or
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Light dev workflow — goal-grounded extension of an existing system.
 

package/skills/boop-refactor-dev-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "When you need to change a contract, cardinality, or shape that exi
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Workflow for refactoring to enable a feature
 

package/skills/boop-stray-disposition/SKILL.md

@@ -4,6 +4,10 @@ description: "When an autonomous run (a loop, a sweep, a sub-agent session) has
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Stray disposition — settle what a run filed before you call it done
 

package/skills/boop-test-audit-workflow/SKILL.md

@@ -4,6 +4,10 @@ description: "Use when a set of tests is not testing the purpose of the code: mo
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
 
 # Test audit workflow — cut the tests that cannot go red, and re-level the rest.
 

package/skills/boop-website-dev-workflow/SKILL.md

@@ -4,6 +4,11 @@ description: "When you are tasked with implementing website changes end-to-end (
 metadata:
   category: workflow
 ---
+> **Read `PROJECT.md`, beside this file, first.**
+> It records how this project applies the guidance below, and where it deliberately differs.
+> Where the two conflict, `PROJECT.md` wins.
+> Record project-specific rules there, never in this file.
+
 # Workflow for building website changes.
 
 This is the **website sibling** of [`boop-feature-dev-workflow`](../boop-feature-dev-workflow/SKILL.md) — same step-by-step flow, same beads-issue structure, customized for marketing-site work (new pages, page rewrites, IA changes, content/CTA updates).