@use-the-fork/spindle 0.0.1 → 0.1.0

package/build/Assets/Blueprints/skills/{setup-project → spindle-project-setup}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: setup-project
-description: "Use after spindle init to document project tooling and establish domain glossaries."
+name: spindle-project-setup
+description: "Use after {{ computed.spindle_package_manager }} spindle init to document project tooling and establish domain glossaries."
 disable-model-invocation: false
 user-invocable: true
 metadata:
@@ -14,7 +14,7 @@ Curate the commands agents should use and establish project domain documentation
 
 ## Prerequisite
 
-The user must have completed `spindle init` before running this skill. This skill
+The user must have completed `{{ computed.spindle_package_manager }} spindle init` before running this skill. This skill
 does not initialize the project. If the required project guidance or tooling
 registry is missing, report the prerequisite and stop.
 
@@ -41,7 +41,7 @@ Also inspect the source to determine whether this is an existing project: it con
 
 ### C. Update and verify tooling
 
-Load and follow the `update-tooling` skill. Supply the verified candidate commands and relevant configuration paths found in B as explicit context, and request a full registry comparison for initial setup. That skill owns the proposal, explicit approval, revision loop, `spindle tool` registry mutations, and generated-guide verification; do not duplicate or bypass its approval gate.
+Load and follow the `spindle-tooling-update` skill. Supply the verified candidate commands and relevant configuration paths found in B as explicit context, and request a full registry comparison for initial setup. That skill owns the proposal, explicit approval, revision loop, `{{ computed.spindle_package_manager }} spindle tool` registry mutations, and generated-guide verification; do not duplicate or bypass its approval gate.
 
 **Complete when:** the delegated workflow has returned with the registry and guide verified, selecting G. If approval is pending, wait; if it reports failures or discrepancies, report the blocker and stop rather than claiming setup is complete.
 

package/build/Assets/Blueprints/skills/{update-tooling → spindle-tooling-update}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: update-tooling
+name: spindle-tooling-update
 description: "Use when tooling commands are added, changed, or removed, or when refreshing the tooling registry and generated guide."
 argument-hint: "[change description or tooling paths]"
 disable-model-invocation: false
@@ -34,7 +34,7 @@ flowchart TD
 
 ### A. Inspect tooling and registry
 
-Read project guidance and run `spindle tool list` from the target Git working tree. Inspect package manifests, task runner configuration, and test/build configuration for the supplied target, or the whole project when no target is supplied. Verify command names, argument forms, and working-directory requirements against configuration. Preserve unrelated registry entries; absence from a targeted inspection is not evidence that an entry is obsolete.
+Read project guidance and run `{{ computed.spindle_package_manager }} spindle tool list` from the target Git working tree. Inspect package manifests, task runner configuration, and test/build configuration for the supplied target, or the whole project when no target is supplied. Verify command names, argument forms, and working-directory requirements against configuration. Preserve unrelated registry entries; absence from a targeted inspection is not evidence that an entry is obsolete.
 
 Do not execute project commands merely to document them if execution could install dependencies, mutate data, or have side effects without authorization. If the registry is missing or invalid, report the prerequisite and stop; do not run initialization or silently repair it.
 
@@ -59,14 +59,14 @@ Ask for explicit approval of the complete change set and wait. Approval applies
 Apply only approved changes through Spindle, not by directly editing the registry or generated Markdown. Add one entry per approved command:
 
 ```sh
-spindle tool add \
+{{ computed.spindle_package_manager }} spindle tool add \
   --key test-unit \
   --section Testing \
   --command "pnpm test -- --run" \
   --description "Run the focused unit tests."
 ```
 
-Use `spindle tool update <key>` with the approved `--section`, `--command`, or `--description` fields; `--clear-description` explicitly removes a description. Use `spindle tool remove <key>` for approved removals. Each successful mutation regenerates the guide, grouped by section with empty sections omitted.
+Use `{{ computed.spindle_package_manager }} spindle tool update <key>` with the approved `--section`, `--command`, or `--description` fields; `--clear-description` explicitly removes a description. Use `{{ computed.spindle_package_manager }} spindle tool remove <key>` for approved removals. Each successful mutation regenerates the guide, grouped by section with empty sections omitted.
 Run project scripts with `{{ computed.spindle_package_manager }} <script>`, such as `{{ computed.spindle_package_manager }} lint`.
 
 If the inspected registry or relevant configuration has changed since approval, stop and return to A, then obtain approval for a refreshed proposal. If a command fails, stop and report the failure and any already-applied changes; do not claim atomicity or completion.
@@ -75,7 +75,7 @@ If the inspected registry or relevant configuration has changed since approval,
 
 ### E. Verify registry and guide
 
-Run `spindle tool list` again and inspect `docs/agents/tooling.md`. Confirm entries, sections, commands, descriptions, and limitations agree, approved changes are reflected, and unrelated entries remain unchanged. After a decline or no-op, verify the existing state without mutating it. Report mismatches; any corrective changes require a new proposal and approval rather than direct Markdown edits.
+Run `{{ computed.spindle_package_manager }} spindle tool list` again and inspect `docs/agents/tooling.md`. Confirm entries, sections, commands, descriptions, and limitations agree, approved changes are reflected, and unrelated entries remain unchanged. After a decline or no-op, verify the existing state without mutating it. Report mismatches; any corrective changes require a new proposal and approval rather than direct Markdown edits.
 
 **Complete when:** verification results and any discrepancies are known, selecting F.
 

package/build/Assets/Templates/project/copilot-instructions.md

@@ -1,14 +1,8 @@
-## Agent skills
+## Issue tracker
 
-### Issue tracker
+SDD specs and tickets live in numbered `.scratch/<feature-id>-<feature-slug>/` workspaces. See `docs/agents/issue-tracker.md` and `docs/agents/ticket-tracker.md` for their conventions.
 
-Repository triage requests are tracked as local Markdown under `.scratch/YYYY-MM-DD-<feature-slug>/`; SDD specs and tickets live in numbered `.scratch/<feature-id>-<feature-slug>/` workspaces. See `docs/agents/issue-tracker.md` and `docs/agents/ticket-tracker.md` for their conventions.
-
-### Triage labels
-
-Use `Category: bug|enhancement` and the five canonical state values in `Status:`. See `docs/agents/triage-labels.md`.
-
-### Domain docs
+## Domain docs
 
 This is a multi-context repo; use `GLOSSARY-MAP.md` to find the relevant context glossary and consult `docs/adr/` for cross-context decisions. See `docs/agents/domain.md`.
 

package/build/Assets/Templates/project/ticket-tracker.md

@@ -15,19 +15,19 @@ Spindle SDD stores feature work in `.scratch/` workspaces. A workspace contains
 Create each approved ticket in dependency order:
 
 ```sh
-spindle sdd ticket create --spec <absolute-spec-path> --title "..." --reporter "..." --category enhancement --author maintainer
+{{ computed.spindle_package_manager }} spindle sdd ticket create --spec <absolute-spec-path> --title "..." --reporter "..." --category enhancement --author maintainer
 ```
 
 The command returns the new ticket ID and path. Complete its template, then set dependencies with `ticket update`:
 
 ```sh
-spindle sdd ticket update --spec <absolute-spec-path> --ticket T-0002 --blocked-by T-0001 --author maintainer
-spindle sdd ticket comment --spec <absolute-spec-path> --ticket T-0001 --details "..." --author maintainer
-spindle sdd ready --spec <absolute-spec-path>
+{{ computed.spindle_package_manager }} spindle sdd ticket update --spec <absolute-spec-path> --ticket T-0002 --blocked-by T-0001 --author maintainer
+{{ computed.spindle_package_manager }} spindle sdd ticket comment --spec <absolute-spec-path> --ticket T-0001 --details "..." --author maintainer
+{{ computed.spindle_package_manager }} spindle sdd ready --spec <absolute-spec-path>
 ```
 
 Use `--clear-blocked-by` to remove dependencies. Use `ticket update --status` to change status. Ticket Markdown remains editable; attributed comments are appended under `## Comments`. Do not add an execution field to the ticket file: execution transitions are recorded in `sdd.json`.
 
 ## Delivery
 
-Use `spindle sdd status` and `spindle sdd ready` to inspect work. Claim and dispatch ready tickets with `spindle sdd claim` and `spindle sdd implement`, submit the assigned report with `spindle sdd submit`, and close completed tickets with `spindle sdd ticket update --status closed`. Follow the `int-subagent-driven-dev` skill for review, correction, and feature completion.
+Use `{{ computed.spindle_package_manager }} spindle sdd status` and `{{ computed.spindle_package_manager }} spindle sdd ready` to inspect work. Claim and dispatch ready tickets with `{{ computed.spindle_package_manager }} spindle sdd claim` and `{{ computed.spindle_package_manager }} spindle sdd implement`, submit the assigned report with `{{ computed.spindle_package_manager }} spindle sdd submit`, and close completed tickets with `{{ computed.spindle_package_manager }} spindle sdd ticket update --status closed`. Follow the `int-subagent-driven-dev` skill for review, correction, and feature completion.

package/build/BlueprintManagement/Commands/Prompts.js

@@ -20,7 +20,7 @@ export async function promptSpindlePackageManager() {
         message: "Which package-manager command should Spindle use in generated guidance?",
         options: [
             { value: "npm run", label: "npm run" },
-            { value: "pnpm", label: "pnpm" },
+            { value: "pnpm exec", label: "pnpm exec" },
             { value: "yarn", label: "yarn" },
             { value: "bun", label: "bun" },
             { value: "other", label: "Other" },

package/build/TemplateRendering/Computed/ComputedVariableProviders.js

@@ -1,6 +1,8 @@
+import { AuthoringFlowchartProvider } from "./Providers/AuthoringFlowchartProvider.js";
 import { InternalSkillDescriptionProvider } from "./Providers/InternalSkillDescriptionProvider.js";
 import { SpindlePackageManagerProvider } from "./Providers/SpindlePackageManagerProvider.js";
 export const computedVariableProviders = {
+    authoring_flowchart: AuthoringFlowchartProvider,
     internal_skill_description: InternalSkillDescriptionProvider,
     spindle_package_manager: SpindlePackageManagerProvider,
 };

package/build/TemplateRendering/Computed/Providers/AuthoringFlowchartProvider.js

@@ -0,0 +1,26 @@
+import { ComputedVariableProvider } from "../ComputedVariableProvider.js";
+export class AuthoringFlowchartProvider extends ComputedVariableProvider {
+    render() {
+        return [
+            "```mermaid",
+            "flowchart TD",
+            '    A["Read and consider only the `int-writing-for-agents` and `asd-ste100` skills"]',
+            '    A --> B["Use the `grill` skill on the user request"]',
+            '    B --> C{"Shared understanding confirmed?"}',
+            '    C -- "No" --> B',
+            '    C -- "Yes" --> D["Load the remaining required skills"]',
+            '    D --> E["Run the core and expanded baselines"]',
+            '    E --> F{"Baseline shows a gap?"}',
+            '    F -- "No" --> J["Report that no change is needed"]',
+            '    F -- "Yes" --> G["Create or update the requested artifact"]',
+            '    G --> H["Run the core and expanded retests"]',
+            '    H --> I{"All criteria pass?"}',
+            '    I -- "No" --> G',
+            '    I -- "Yes" --> K["Report the artifact and validation"]',
+            "```",
+            "",
+            "During the grill exchange, ask one question per turn and wait for the answer.",
+            "Do not load other skills or announce the current flowchart step until the user confirms shared understanding.",
+        ].join("\n");
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@use-the-fork/spindle",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "description": "",
   "keywords": [],
   "license": "ISC",