Skip to content

T-521G-pilot-consumer-polish

Status: closed/obsoleted · Impact: high · Complexity: large

The whole D-0014 chain — dist-repo install, both doors, doctor, CI — gets its first real consumer. The polish repo has been waiting on exactly this pinnable artifact since its user-level SDLC install was torn down (2026-06-01). The pilot also carries a decision: it resolves D-0014’s open question on where the installed plugin lives (repo-local copy vs node_modules pointer) by trying both.

LocationRole today
docs/planning/decisions/D-0014-cli-primary-npm-distribution.mdopen question “Where the installed plugin lives” awaits the pilot’s verdict; “Dogfooding the consumer path” partially answered by this task
docs/planning/tasks/T-ZF8U-harness-install-claude-verb.mdspec of the install verb the pilot exercises in both modes
README.md(T-75UD) consumer install instructions the pilot follows verbatim — deviations are documentation bugs

The polish repo itself (separate checkout under the same account) has no SDLC wiring today; its pinning was deferred in project memory pending this artifact.

Polish consumes SDLC exactly the way D-0014 describes: dep pinned to a dist-repo tag, sdlc project setup scaffolding, harness installed via the verb, doctor green, a polish CI job running sdlc gates with the documented read credential, and a Claude session in polish driving skills from the pinned plugin. Every friction point lands as a backlog item; the plugin-home decision lands back in D-0014.

  1. In polish: bun add -d git+ssh://git@github.com/sksizer/sdlc-dist#v0.3.0; commit lockfile.
  2. bunx sdlc project setup (scaffold docs/planning/, sdlc.yaml); run /sdlc:find-quality-checks-equivalent config for polish’s own gates (or hand-set a minimal quality_checks: list).
  3. bunx sdlc harness install claude (default copy mode). Open a Claude Code session in polish: confirm the sdlc plugin loads from .sdlc/plugin/, /sdlc:info reports the pinned version, and two skills run end to end (/sdlc:task-new, /sdlc:backlog-capture).
  4. Re-install with --mode node-modules; repeat the session check. Record which mode survives real use better (plugin-cache behavior, bun install churn, path stability) — this is the D-0014 open-question verdict.
  5. bunx sdlc project doctor green in the winning mode; tamper test (bump the dep without re-running install) shows the doctor mismatch FAIL, then re-install clears it.
  6. Polish CI: add a job installing the git dep with the documented read credential and running npx sdlc entities audit (plus polish’s quality roster if configured). Node-only variant: one CI run with Bun absent proves the consumer floor.
  7. Record outcomes in this repo: D-0014 open question resolved in place (winning mode + rationale, per the rewrite-in-place convention); sdlc backlog create one item per friction point hit during steps 1-6.
  8. Close the loop on the deferred polish pin noted in project memory.
LocationKindChange
docs/planning/decisions/D-0014-cli-primary-npm-distribution.mdmodifyresolve the plugin-home open question with the pilot verdict; note the pilot completion under Migration step 7
docs/planning/backlog/modifyone captured item per friction point (via sdlc backlog create)
README.mdmodifycorrections for any install-instruction step that deviated in practice

(The polish-repo changes — dep, scaffolding, CI job, settings — live in the polish repo and are enumerated in this task’s Approach, not this table.)

  • AC-1: polish’s lockfile pins the dist-repo tag; bunx sdlc --help and npx sdlc --help (Bun absent) both exit 0 in the polish checkout.
  • AC-2: a Claude Code session in polish lists the sdlc skills from the installed plugin, and two skills complete end to end against polish’s docs/planning/.
  • AC-3: sdlc project doctor passes in the chosen mode, and fails with the version-mismatch message after a dep bump without re-install.
  • AC-4: a polish CI run installs the git dep with the documented credential and passes npx sdlc entities audit under Node without Bun.
  • AC-5: D-0014’s “Where the installed plugin lives” open question is rewritten in place with the verdict and rationale.
  • AC-6: every friction point encountered is a backlog item (zero verbal-only findings).
  • Fixing non-blocking friction found during the pilot — captured as backlog, triaged separately.
  • Site generation in polish (T-0PIB pilots that separately if polish wants a docs site).
  • Onboarding further consumers — the pilot’s README corrections are the repeatable path.
  • T-ZF8U and T-75UD (hard, in depends_on): needs the install verb and a consumable release tag. Transitively T-WGV4, T-ITMN, T-XTGT, T-T0O9 — the pilot is the integration test of the whole wave.
  • D-0014 Migration step 7; polish named there as the candidate. The deferred polish reinstall is recorded in project memory (user-level install torn down 2026-06-01, pin deferred pending a tagged artifact).

T-ZF8U-harness-install-claude-verb, T-75UD-release-ci-dist-repo


← Back to Tasks