fix: correct installed preset paths and reviewer binding model

docs/spec-kit-workflow/architecture.md

@@ -7,7 +7,7 @@ grounded planning, optional human review, reviewed execution decomposition,
 explicit human approval, and delegated implementation through a versioned
 Markdown protocol. The preset is provider-neutral: it defines command and
 artifact contracts, while the active coding integration supplies concrete
-workers, models, skills, and permissions. Its preset version is `0.2.1` and its
+workers, models, skills, and permissions. Its preset version is `0.4.0` and its
 protocol version is `0.1.0`; it supports Spec Kit `>=0.12.11` without an upper
 support boundary.
 
@@ -81,7 +81,7 @@ dispatch, or writes. It fails closed only below the minimum, on an explicit
 installed-manifest exclusion, or when a required contract is missing, malformed,
 or incoherent. Newer untested CLI versions neither warn nor block. This protects
 generated commands that remain in a project after the CLI changes without
-changing required public integration behavior. The accepted execution-plan
+changing required public integration behavior. The accepted execution-package
 protocol is likewise `0.1.0`; unsupported or malformed protocol artifacts return
 to their owning generation command rather than being migrated or inferred.
 
@@ -93,25 +93,35 @@ The preset deliberately uses different integration strategies by phase:
 - `/speckit.plan` and `plan-template` compose with upstream planning, retaining
   its design artifacts, adding verified grounding and integration context, and
   offering optional human review at natural completion.
-- `/speckit.tasks`, `tasks-template`, `/speckit.analyze`, and
-  `/speckit.implement` replace their upstream surfaces because decomposition,
-  independent review, approval, and delegated execution share a stronger
-  protocol.
-- Auxiliary templates provide the execution plan, cumulative review reports,
-  aggregate analysis, and local progress ledger used by those replacements.
+- `/speckit.tasks`, `tasks-template`, and `/speckit.implement` replace their
+  upstream surfaces because decomposition, independent review, approval, and
+  delegated execution share a stronger protocol. The preset provides no
+  `/speckit.analyze`; it folds independent review and human approval into
+  `/speckit.plan` and `/speckit.tasks`. The stock `/speckit.analyze` resolves from
+  a lower layer and is not part of this lifecycle.
+- Auxiliary templates provide the indexed sub-plans, cumulative review reports,
+  and local progress ledger used by those replacements.
+
+The preset does not run Spec Kit extension hooks. Stock command bodies dispatch
+`before_*` and `after_*` hooks from `.specify/extensions.yml`. The preset
+replacements omit that mechanism, so no phase runs an extension automatically. The
+git extension branch and commit hooks never fire from the workflow. An operator
+runs an extension command manually when wanted.
 
 The installed preset references are the normative source for workflow behavior,
-artifact schemas, and CLI/package compatibility. In particular,
-[protocol compatibility][compatibility] owns the minimum-version and structural
-package-integrity contract. This architecture overview summarizes those
-boundaries without redefining them.
+artifact schemas, and CLI/package compatibility. The minimum supported version and
+the structural package-integrity contract come from the installed manifest and its
+`requires.speckit_version`, as described in the Package-Integrity Command Boundary
+section above. This architecture overview summarizes those boundaries without
+redefining them.
 
 ### Optional Human Review
 
 At the natural completion of specification and planning, after artifacts are
 generated and validated, each phase independently offers a guided walkthrough
 or independent review. Either can be declined. The interaction stores no
-preference, approval record, or workflow gate, and does not apply to analysis.
+preference, approval record, or workflow gate, and does not apply to the
+independent review or approval gates.
 The installed `human-review.md` reference owns the mechanics: select small,
 consequential review units using judgment; pause after each; update and
 revalidate current-phase artifacts once a unit is settled; then continue normal
@@ -128,15 +138,16 @@ The protocol separates durable planning truth from local runtime evidence:
   inputs.
 - `tasks.md` is the sole atomic task ledger. It owns task identity, task text,
   paths, story labels, task-local parallel hints, and completion checkboxes.
-- `execution-plan.md` owns execution groups, the dependency graph and order,
+- The indexed `subplans/` own execution groups, the dependency graph and order,
   file ownership, cross-group contracts and data flow, semantic model tiers,
   required skills and capabilities, tests, acceptance criteria, and
   verification.
 - `specs/<feature>/reviews/<role-id>.md` files are tracked cumulative sources of
   reviewer findings. Reruns append current-state rounds rather than replacing
   review history.
-- `analysis.md` is the tracked aggregate of applicable review rounds and the
-  location of the explicit human approval decision.
+- The human approval decisions live in their owning artifacts: Design Acceptance
+  in `plan.md` and Implementation Authorization in `tasks.md`. The preset produces
+  no separate `analysis.md` aggregate.
 - `specs/<feature>/progress.md` is an ignored local ledger for concrete workers
   and models, workspaces, dispatch and test evidence, checkpoints, blockers,
   failures, integration state, and resume decisions. It does not duplicate
@@ -148,29 +159,29 @@ artifacts while preserving a reviewable decomposition and approval record.
 ## Planning And Review Flow
 
 Task generation reads the specification, plan, and available design artifacts,
-then creates `tasks.md` and `execution-plan.md` as one normalized pair. It
-validates the pair before writing either artifact, so task descriptions and
-checkboxes remain in the task ledger while execution policy remains in the
-orchestration plan.
-
-Before semantic review, analysis consumes the shared installed structural
-validator. Structural failure blocks before reviewer dispatch or report writes.
-After a successful preflight, the coordinator requires independent
-fresh-context reviews from:
-
-- Mid-tier `artifact-fidelity`, which traces the approved inputs into the
-  planned work;
-- Most capable `decomposition-design`, which judges execution feasibility and
-  decomposition quality; and
-- Mid-tier `plan-clarity`, which judges whether the handoff is unambiguous to a
-  cold reader.
-
-Projects may select additional project-owned reviewer packets. Each required
-role writes to its cumulative report, and the coordinator preserves source
-finding ownership while producing `analysis.md`. The coordinator validates and
-aggregates reviewer output but does not perform a fallback semantic review.
-Implementation remains blocked until the latest run is complete and the human
-approval record authorizes it.
+then creates `tasks.md` and its indexed `subplans/` as one normalized set. It
+validates the set before writing, so task descriptions and checkboxes remain in
+the task ledger while execution policy remains in the sub-plans.
+
+Independent review runs inside two phases, not a separate command. Each producing
+phase dispatches fresh-context, read-only reviewers and blocks its own human
+approval until the reviews permit it:
+
+- `/speckit.plan` requires most-capable `rfc-design`, which judges technical
+  coherence of the RFC, and mid-tier `rfc-clarity`, which judges cold-reader
+  clarity of the RFC. Both feed Design Acceptance in `plan.md`.
+- `/speckit.tasks` requires mid-tier `tasks-rfc-fidelity`, which traces the
+  accepted RFC and Feature Definition into the task package, and most-capable
+  `tasks-executability`, which judges decomposition feasibility and testable
+  work. Both feed Implementation Authorization in `tasks.md`.
+
+Before task review, the shared installed structural validator runs first. A
+structural failure blocks before reviewer dispatch or report writes. Projects may
+select additional project-owned reviewer packets. Each role appends to its
+cumulative report under `specs/<feature>/reviews/`, and the producing phase
+preserves source finding ownership. No phase performs a fallback self-review, and
+no phase produces an `analysis.md` aggregate. Implementation remains blocked until
+the latest reviews are complete and the recorded human approval authorizes it.
 
 ## Delegated Implementation Flow
 
@@ -210,19 +221,23 @@ dispatch evidence stays in ignored progress or transient runtime state.
 Suitability checks inspect runtime metadata and configuration only. Preflight
 does not invoke a worker, calibration task, probe, canary, or sacrificial call.
 The first worker invocation carries the real assigned review or implementation
-work. Missing evidence for tier, concrete model, skills, permissions,
-invokability, fresh context or attribution, workspace targeting, dispatch, or
-result identity blocks the applicable role or group.
+work. Missing evidence for tier, concrete model, permissions, invokability, fresh
+context or attribution, workspace targeting, dispatch, or result identity blocks
+the applicable role or group. A reviewer role additionally requires a read-only
+workspace and a single candidate whose description matches the role. An
+implementation group additionally requires the skills and capabilities that the
+sub-plan names.
 
 ## Failure And Recovery Boundaries
 
 The protocol fails closed at ownership boundaries rather than repairing state
 in a later phase:
 
 - Unsupported, missing, or malformed task/execution artifacts are regenerated
-  by `/speckit.tasks`; invalid review reports or aggregate state return to
-  `/speckit.analyze` with explicit confirmation where history could be lost.
-- An incomplete analysis run or a role marked `Recovery required` blocks
+  by `/speckit.tasks`; invalid review reports or approval state return to their
+  producing phase (`/speckit.plan` or `/speckit.tasks`) with explicit
+  confirmation where history could be lost.
+- An incomplete review round or a role marked `Recovery required` blocks
   implementation. Ambiguous started invocations are retained for explicit
   recovery and are not automatically redispatched.
 - Unsafe worker binding, worktree targeting, dirty state, test evidence,
@@ -254,12 +269,11 @@ operation. Runtime review, binding, and implementation remain **Not exercised**
 until a normal feature completes them with real assigned work.
 
 See the [preset README][preset-readme] for installation and diagnostic commands.
-[Protocol compatibility][compatibility], [artifact validation][artifact-validation],
-[analysis and approval][analysis], and [execution lifecycle][execution] define
-their respective installed protocol contracts.
+[Artifact contracts][artifact-contracts], [review lifecycle][review-lifecycle],
+and [execution lifecycle][execution] define their respective installed protocol
+contracts.
 
 [preset-readme]: ../../private_dot_config/specify/presets/timors-agentic-workflow/README.md
-[compatibility]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/protocol-compatibility.md
-[artifact-validation]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/artifact-validation.md
-[analysis]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/analysis-and-approval.md
+[artifact-contracts]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/artifact-contracts.md
+[review-lifecycle]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/review-lifecycle.md
 [execution]: ../../private_dot_config/specify/presets/timors-agentic-workflow/references/execution-lifecycle.md

private_dot_config/specify/presets/timors-agentic-workflow/README.md

@@ -1,6 +1,6 @@
 # Timor's Agentic Workflow
 
-Preset `0.3.0` supplies one project-installed lifecycle:
+Preset `0.4.0` supplies one project-installed lifecycle:
 
 `specify` → `clarify` when Draft → `plan` → `tasks` → `implement`.
 
@@ -34,12 +34,14 @@ operator-controlled, not a workflow command gate.
 
 ## Execution Boundaries
 
-Task packages contain provider-neutral tiers and exact skills, not concrete
-workers, model IDs, credentials, local workspace paths, or dispatch identities.
-Binding is just in time and requires tier, skills, discoverability, invokability,
-correct workspace targeting, and attributable results. Project-local candidates
-are preferred; ambiguity requires a human choice. Runtime considerations neither
-grant access nor alter eligibility.
+Task packages contain provider-neutral tiers and the skills each group needs, not
+concrete workers, model IDs, credentials, local workspace paths, or dispatch
+identities. Binding is just in time. An implementation group requires its tier,
+skills, discoverability, invokability, correct workspace targeting, and
+attributable results. A reviewer role requires its tier, a read-only workspace,
+and a single candidate whose description matches the role. Project-local
+candidates are preferred; ambiguity requires a human choice. Runtime
+considerations neither grant access nor alter eligibility.
 
 Each packet has a dedicated branch and worktree. Workers may commit only there;
 the coordinator alone advances the active branch. The approved tracked feature

private_dot_config/specify/presets/timors-agentic-workflow/commands/speckit.clarify.md

@@ -4,9 +4,11 @@ description: Converge a Feature Definition through one-question human dialogue.
 
 ## Authority and Inputs
 
-Read canonical `spec.md`, `references/artifact-contracts.md`,
-`references/feature-definition.md`, `references/clarification.md`, and
-`references/review-lifecycle.md`. `spec.md` is the only authority for product
+Resolve the canonical feature directory from `.specify/feature.json` per
+`.specify/presets/timors-agentic-workflow/references/artifact-contracts.md` before
+any read. Read canonical `spec.md`, `.specify/presets/timors-agentic-workflow/references/artifact-contracts.md`,
+`.specify/presets/timors-agentic-workflow/references/feature-definition.md`, `.specify/presets/timors-agentic-workflow/references/clarification.md`, and
+`.specify/presets/timors-agentic-workflow/references/review-lifecycle.md`. `spec.md` is the only authority for product
 intent. Do not inspect repository reality or make technical design choices.
 
 ## Procedure

private_dot_config/specify/presets/timors-agentic-workflow/commands/speckit.implement.md

@@ -6,31 +6,34 @@ description: Execute approved sub-plans in isolated worktrees and integrate pack
 
 Require Ready canonical `spec.md`; canonical `plan.md` Design Acceptance Accepted
 for its current Revision; a closed, reviewed `tasks.md`; `authorization: approved`;
-and a fully clean, named, stable active branch. Read
-`references/artifact-contracts.md`, `references/execution-lifecycle.md`,
-`references/workspace-isolation.md`, `references/scheduling-policy.md`,
-`references/model-and-worker-selection.md`, `references/testable-work.md`, and
-`references/documentation-planning.md`. Use `templates/progress-template.md` and,
-when required, `reviewers/component-docs.md` with
-`templates/review-report-template.md`.
+and a fully clean, named, stable active branch. Resolve the canonical feature
+directory from `.specify/feature.json` per
+`.specify/presets/timors-agentic-workflow/references/artifact-contracts.md` before
+reading any artifact. Read
+`.specify/presets/timors-agentic-workflow/references/artifact-contracts.md`, `.specify/presets/timors-agentic-workflow/references/execution-lifecycle.md`,
+`.specify/presets/timors-agentic-workflow/references/workspace-isolation.md`, `.specify/presets/timors-agentic-workflow/references/scheduling-policy.md`,
+`.specify/presets/timors-agentic-workflow/references/model-and-worker-selection.md`, `.specify/presets/timors-agentic-workflow/references/testable-work.md`, and
+`.specify/presets/timors-agentic-workflow/references/documentation-planning.md`. Use `.specify/presets/timors-agentic-workflow/templates/progress-template.md` and,
+when required, `.specify/presets/timors-agentic-workflow/reviewers/component-docs.md` with
+`.specify/presets/timors-agentic-workflow/templates/review-report-template.md`.
 
 ## Procedure
 
-1. Perform the concrete phase checks in `references/execution-lifecycle.md`; do
+1. Perform the concrete phase checks in `.specify/presets/timors-agentic-workflow/references/execution-lifecycle.md`; do
    not redesign the approved package. Resolve, pin, and later refresh signing
-   policy exactly under `references/workspace-isolation.md`. Add the exact local
+   policy exactly under `.specify/presets/timors-agentic-workflow/references/workspace-isolation.md`. Add the exact local
    progress path to `.git/info/exclude` after clean preflight, then create initial
    progress from its template. Creation is the lock event and records active branch,
    starting commit, complete protected baseline, and policy evidence.
 2. For each ready canonical identity, validate closed package structure, selected
    tracked regular file, predecessor status and contract evidence, ownership, test
    mode/basis, and baseline equality. Bind a worker under
-   `references/model-and-worker-selection.md`. Create a dedicated branch/worktree,
+   `.specify/presets/timors-agentic-workflow/references/model-and-worker-selection.md`. Create a dedicated branch/worktree,
    derive and record its worktree-root-relative locator, and dispatch only the
    identity, locator, invocation-specific constraints, prerequisite evidence,
    recovery context, and limited result envelope. Do not copy packet prose into
    the prompt.
-3. Let `references/scheduling-policy.md` control waves. Workers may browse but not
+3. Let `.specify/presets/timors-agentic-workflow/references/scheduling-policy.md` control waves. Workers may browse but not
    expand authority, modify protected feature files, rewrite history, merge
    unrelated work, or push. Validate returned changed paths, commits, verification,
    output evidence, runtime outcomes, attribution, clean branch, and baseline at