@maestria/cursor 0.2.11 → 0.2.12

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "maestria",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "description": "Maestria methodology for Cursor - pipeline specialists, orchestrator skill, and workflow commands",
   "author": {
     "name": "agustinusnathaniel"

package/README.md

@@ -1,6 +1,6 @@
 # @maestria/cursor
 
-A declarative [Cursor](https://cursor.com/) plugin that brings Maestria's structured agent orchestration to Cursor IDE and Cursor CLI (`agent`; `cursor-agent` is a compatibility alias) - 7 specialist Task agents, an orchestrator skill, always-on global rules, and workflow commands.
+A declarative [Cursor](https://cursor.com/) plugin that brings Maestria's structured agent orchestration to Cursor IDE and Cursor CLI (`agent`; `cursor-agent` is a compatibility alias) - specialist Task agents, an orchestrator skill, always-on global rules, and workflow commands (7 specialists as of 2026-09-22; see What It Provides below for the current list).
 
 > This package is part of the Maestria project. See [VISION.md](https://github.com/agustinusnathaniel/maestria/blob/main/VISION.md) for the project vision, motivation, and scope.
 
@@ -15,10 +15,11 @@ Restart Cursor IDE (or use **Developer: Reload Window**). Cursor CLI uses `agent
 
 ## What It Provides
 
-- **7 specialist Task agents** - adventurer, architect, builder, diagnose, planner, reviewer, writer.
+- **Specialist Task agents** (7 as of 2026-09-22; see the [package directory](https://github.com/agustinusnathaniel/maestria/blob/main/packages/cursor/agents) for the current list) - adventurer, architect, builder, diagnose, planner, reviewer, writer.
 - **Orchestrator skill** - dispatcher methodology, handoff contracts, maker/checker guidance.
 - **Always-on global rules** - `rules/maestria-global.mdc` with `alwaysApply: true`.
 - **Workflow commands** - `/fein` (full pipeline), `/sonar` (research only), `/blitz` (fast implementation).
+- **Project customization (advisory)** - the orchestrator reads project-root `.maestria/workflow.md` then `.maestria/rules.md` with host tools when not already supplied; missing files leave defaults unchanged, and an unreadable file is disclosed and requested rather than invented.
 
 ## Support / Platform Notes
 

package/agents/planner.md

@@ -44,4 +44,4 @@ Include planned phases, assumptions, verification and rollback evidence, and the
 
 ## Skills
 
-Use available skill descriptions for unresolved requirements, product discovery, issue/PRD creation, or prototyping when that work is part of the assignment. Skip skill loads for one-step plans.
+Use available skill descriptions for unresolved requirements, product discovery, issue/PRD creation, or prototyping when that work is part of the assignment. See the available `spec-contract` skill for an optional contract header shape. Skip skill loads for one-step plans.

package/agents/reviewer.md

@@ -82,6 +82,10 @@ Use these categories to identify relevant risks. Cover the changed contract and
 - Does the output read like a professional email to a trusted colleague?
 - Format findings as: `style: [issue] -> [fix/dismiss]`
 
+### 10. Spec-contract drift (optional pointer, skip when absent)
+
+- When a spec-contract header or owning spec is linked, apply its drift, acceptance-coverage, ambiguity-tagging, delta-stating, and append-only rules; skip when absent.
+
 ## Questions to Ask Yourself
 
 1. Is this specific code change related to the overall intended goal?
@@ -132,7 +136,7 @@ Then produce:
 
 ## Skills
 
-For interface changes, use UI review guidance; for interaction or access risks, accessibility guidance; for page discovery/sharing, metadata guidance; for animation issues, motion guidance. Load `skill-judge` for skill packages. Skip unrelated loads for backend or infrastructure diffs.
+For interface changes, use UI review guidance; for interaction or access risks, accessibility guidance; for page discovery/sharing, metadata guidance; for animation issues, motion guidance. See the available `spec-contract` skill for an optional contract header shape. Load `skill-judge` for skill packages. Skip unrelated loads for backend or infrastructure diffs.
 
 ## References
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maestria/cursor",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "private": false,
   "description": "Maestria methodology plugin for Cursor IDE and Cursor CLI - specialists, orchestrator, and workflow commands",
   "keywords": [

package/rules/maestria-global.mdc

@@ -39,9 +39,8 @@ At acceptance, classify visual evidence as required (changed surfaces, relevant
 
 ### Documentation and changesets
 
-- Assess internal docs, user-facing docs, changelog/release notes, and required changesets separately; update only affected categories, with a concise reason when a plausible category needs no update.
-- Carry required documentation through implementation and review briefs to final reconciliation; missing affected docs leaves acceptance incomplete.
-- Keep the assessment proportionate to the change.
+- Required affected docs are part of acceptance; carry them through briefs to final reconciliation.
+- When docs work applies, load the available `docs-update` methodology skill and follow it; a missing skill never blocks ordinary docs work.
 
 Keep file, package, and runtime scope explicit. Classify findings as in-scope defects, design blockers, platform limitations, or follow-ups, and do not expand scope for adjacent findings unless they invalidate acceptance or create an immediate safety or production risk. Freeze the outcome, acceptance criteria, non-goals, and repair limits at the start of a work unit; re-plan only when the outcome or evidence changes.
 
@@ -81,26 +80,7 @@ Merge, release, and production operations remain separate authorization boundari
 
 ### PR delivery contract
 
-Shape every reviewable PR with a title written as an explicit Conventional Commits title (not inferred from commit format) and a body using literal `##` headings in this order:
-
-1. `## Summary` (what changed and why):
-   - Lead with the user-visible outcome, or the maintainer benefit for internal changes, in plain language.
-   - Keep it a short paragraph or a few concise bullets; put file-level details in Changes and check results in Verification.
-   - Omit internal execution metadata such as session IDs; write for a human reviewer.
-2. `## Changes` (Work Results table with File, What changed, and Why columns):
-   - Describe the actual change and its practical purpose, not the editing action.
-   - Group related files that share one change and rationale; skip repeating the Summary and list only symbols that help review.
-   - Omit internal execution metadata such as session IDs; write for a human reviewer.
-3. `## Verification` (checks run, results, and unresolved acceptance gaps)
-   - Note review outcome briefly without pasting identifiers.
-4. `## Visual evidence` when applicable (per the visual-delivery contract)
-5. `## Breaking changes` when applicable (migration guidance)
-
-When the project defines an explicit template, follow it while preserving that required information.
-
-The reviewer checks rendered coverage against the changed surface; the delivery owner reads back the published body to confirm accessible artifacts, captions, and current coverage.
-
-After any push that changes the cumulative diff or verification evidence, update the PR title and body to match, then read back the published body before reporting delivery complete.
+Core owns the outcome, evidence, review, and authorization floors for every reviewable PR. Title, body, and visual-evidence conventions live in the `create-pull-request` methodology skill: for an active PR task, load the available skill before drafting, and follow the project template when one applies while preserving the required information. Stop on explicit project opt-out. A missing skill never blocks delivery and never waives review or authorization; write a sensible body instead. The reviewer checks rendered coverage against the changed surface; after any push that changes diff or verification, refresh the draft and read back the published body before reporting delivery complete.
 
 ## Canonical Source Invariant
 

package/skills/orchestrator/SKILL.md

@@ -56,7 +56,9 @@ Approve when acceptance evidence is complete and no blocking/material finding re
 
 ## Workflow and Delegation
 
-When present, load `.maestria/workflow.md` and `.maestria/rules.md` once per session. Briefs contain only the material needed to act - goal, constraints, acceptance evidence, termination condition - and restate binding user constraints so they survive the hop. Carry required documentation per the global documentation and changesets contract. Fan out only independent, non-overlapping work and integrate all results before review. If the user rejects an approach twice, stop and re-evaluate. Keep assumptions, evidence, and findings separate; re-plan when the outcome or its evidence changes, not merely because activity stalled.
+When the host has not already supplied them, load project-root `.maestria/workflow.md` then `.maestria/rules.md` using host tools (root only). Absence is normal; an unreadable file is surfaced and its content requested rather than silently overridden. Treat both as subordinate guidance under global safety and host authorization. Briefs contain only the material needed to act - goal, constraints, acceptance evidence, termination condition - and restate binding user constraints so they survive the hop. Carry required documentation per the global documentation and changesets contract. Fan out only independent, non-overlapping work and integrate all results before review. If the user rejects an approach twice, stop and re-evaluate. Keep assumptions, evidence, and findings separate; re-plan when the outcome or its evidence changes, not merely because activity stalled.
+
+Load the available `spec-contract` skill only when persistent intent across steps would reduce risk; absence is normal.
 
 ## Mode Precedence
 
@@ -97,16 +99,7 @@ Report briefly at milestones: outcome, verification limits, delivery state, and
 
 ## Visual Delivery Evidence
 
-For changes to rendered UI, including documentation sites and visible CLI output, apply this section when planning verification and include the evidence requirement in implementation and review briefs, with the acceptance classification (required surfaces, states, and evidence, or not applicable with reason).
-
-- Capture the affected screen or interaction, including relevant responsive or state variants, using an available browser or capture tool. A missing desktop display alone does not rule out headless capture. For text-only CLI output, a representative terminal transcript can be sufficient. If vision is available, inspect the capture; otherwise label it visually unverified. Preserve the local artifact at any workable path, including /tmp; do not auto-commit screenshots unless project policy requires it.
-- Hand off implementer evidence as paths plus captions plus coverage gaps: each artifact states what it shows and which variants remain unchecked. The reviewer checks that coverage against the changed surface before delivery.
-- Publish required evidence in the PR body as an attachment or accessible artifact link with a descriptive caption, using supported authorized tooling; check the delivery tool's current help for upload support instead of relying on cached syntax. If upload is unavailable, preserve the local artifact, give its path in the handoff, and state the PR attachment limitation. Capture and upload are separate capabilities.
-- Present evidence concisely by changed screen or behavior: label each artifact with its state and relevant viewport or theme. Use a before/after table when comparison helps and a short captioned list for a single state or when tables would shrink images. Pair comparable captures with matching viewports and states, name the intended difference, disclose missing baselines or unchecked variants without fabricating them, and keep representative captures in the main section with supplemental captures in a collapsible section when supported.
-- Read back the actual PR body as delivery owner before claiming delivery or re-delivery; confirm attachments render or links resolve and evidence matches the current relevant diff. When a later change affects captured appearance or behavior, replace affected captures, update captions and comparisons, and remove obsolete or redundant PR body references; keep intentional clearly labeled before baselines and never present a historical before as current. Refresh only affected evidence, not every commit or unrelated file. Readback is a delivery-owner check, not a second full review.
-- For applicable changes, report evidence captured, unavailable with the checked limitation, or unnecessary with a concrete reason. Source-only documentation edits and mechanical moves preserving rendering can use existing evidence; a refactor label or passing build alone does not establish unchanged visuals. Keep capture effort proportionate to the changed surface.
-
-**!!! For changes requiring visual evidence,** do not claim delivery complete until the evidence is published in the PR body and the delivery owner has read back that body to verify its inclusion. Local paths, session-log references, and comments alone do not satisfy this requirement. If publication is blocked, report visual acceptance as incomplete with the exact checked limitation. An explicit user or project requirement for visual evidence remains acceptance work: provide it or report the outcome incomplete with the exact blocker. Optional PR illustration may be omitted with a reason; required evidence cannot silently become a follow-up.
+For changes to rendered UI, including documentation sites and visible CLI output, classify visual evidence as required (changed surfaces, relevant states, expected evidence) or not applicable with a concrete reason, include the evidence requirement in implementation and review briefs, and load the available `create-pull-request` skill for the capture, handoff, publication, and readback procedure before claiming delivery. Follow the project template when one applies; stop on explicit project opt-out. Missing required evidence blocks acceptance: report it incomplete with the checked limitation, and a missing skill never waives it.
 
 
 ## Specialist Agents (Cursor)