@lab43/q 0.6.0 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lab43/q",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "An agentic coding workflow framework: skills for planning, implementing, verifying, and grooming, grounded in per-project conventions docs.",
   "q": {
     "description": "The rules of the q workflow, governing how a project's work gets planned, decided, documented, and shipped."

package/q-extension/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "q",
   "displayName": "q",
   "description": "An agentic coding workflow framework: skills for planning, implementing, verifying, and grooming, grounded in per-project conventions docs.",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "author": { "name": "Cameron Spencer", "email": "cameron@lab43.com" },
   "license": "MIT"
 }

package/q-extension/conventions/conventions.md

@@ -1,6 +1,6 @@
 # Conventions
 
-Rules for a project's conventions docs: the tiers they come in and which tier wins, what a conventions doc holds, and when a rule leaves prose for a stronger enforcement rung.
+Rules for how a project's conventions are tiered, written, and enforced.
 
 ## Three tiers of conventions
 

package/q-extension/conventions/plans.md

@@ -1,6 +1,6 @@
 # Plans
 
-Format, sequencing, and lifecycle rules for `docs/plans/` documents. `/q:create-plan` writes to this rubric and its adversarial plan reviews enforce it; `/q:implement-plan` executes the delivery shape the plan records.
+Rules for how a project's plans are written, sequenced, and carried to completion. `/q:create-plan` writes to this rubric and its adversarial plan reviews enforce it. `/q:implement-plan` executes the delivery shape the plan records.
 
 ## Audience
 

package/q-extension/conventions/specs.md

@@ -1,6 +1,6 @@
 # Specs
 
-Rules for `docs/specs/` documents: what a spec holds, how it is written, and how the code is held to it. A spec states what the product commits to. Whether a rule is a spec's or a convention's is the taxonomy's call (see: @lab43/q conventions/documentation.md, Taxonomy).
+Rules for how a project's specs are written and how the code is held to them. A spec states what the product commits to. Whether a rule is a spec's or a convention's is the taxonomy's call (see: @lab43/q conventions/documentation.md, Taxonomy).
 
 ## Format
 

package/q-extension/references/agent-briefing.md

@@ -13,7 +13,7 @@ This project follows q, an agentic coding workflow. Its rules live in the projec
 
 If the session's skill list has no `/q:` skills, this machine is missing the q plugin — ask the user to install the project's dependencies (`npm install`, or the project's package manager's equivalent), then run `/q:reconcile`.
 
-When another session is already working this repo, take a worktree rather than sharing the checkout.
+When another session is already working this repo, take a worktree rather than sharing the checkout (source: @lab43/q references/run-contract.md, The delivery branch).
 
 Conventions come in three tiers: q's own, the conventions of any installed extensions, and this project's own `docs/conventions/` (source: @lab43/q conventions/conventions.md, Three tiers of conventions). q and the extensions are dependencies in `package.json`. Project rules win over an extension's rule, and an extension's rule wins over q's. Check all three tiers before writing code, before design decisions and reviews, and before changing docs. Doc changes — the README and this briefing itself included — go through `/q:update-docs`.
 
@@ -23,10 +23,10 @@ Package doc paths are package name plus path from the package's `q-extension/` p
 
 - `@lab43/q conventions/principles.md` — cross-cutting rules for any design decision, plan, or review
 - `@lab43/q conventions/documentation.md` — what belongs in a project's documentation, where it lives, and how it stays accurate
-- `@lab43/q conventions/conventions.md` — rules for a project's conventions docs: the tiers they come in and which tier wins, what a conventions doc holds, and when a rule leaves prose for a stronger enforcement rung
+- `@lab43/q conventions/conventions.md` — how a project's conventions are tiered, written, and enforced
 - `@lab43/q conventions/extensions.md` — the extension format: rules for authoring and publishing a q extension
-- `@lab43/q conventions/plans.md` — format, sequencing, and lifecycle rules for `docs/plans/` documents
-- `@lab43/q conventions/specs.md` — rules for `docs/specs/` documents: what a spec holds, how it is written, and how the code is held to it
+- `@lab43/q conventions/plans.md` — how a project's plans are written, sequenced, and carried to completion
+- `@lab43/q conventions/specs.md` — how a project's specs are written and how the code is held to them
 - `@lab43/q conventions/issue-tracking.md` — rules for working a project's issue tracker from any session
 - `@lab43/q conventions/pull-requests.md` — rules for authoring a pull request
 - `@lab43/q conventions/writing.md` — rules for writing prose: docs, plans, PR bodies, anything a human or agent will read

package/q-extension/skills/install/SKILL.md

@@ -97,7 +97,7 @@ The invocation is the agreement — scaffold autonomously; on a fully set-up, un
 8. **The README's q section** — when the README doesn't mention q, add this section verbatim:
 
    ```markdown
-   ## Claude Code
+   ## Working with q
 
    This project uses [q](https://www.npmjs.com/package/@lab43/q), an agentic coding workflow that grounds Claude Code sessions in the project's own conventions. It arrives with the project's dependencies, and Claude Code loads it from the repo's tracked settings.