"Add a feature to the roadmap and update every plan to match: scores clarity, interviews when unclear, has the lead write it into the end state with acceptance criteria, and opens a plan PR. Use for add a feature or put this on the roadmap."
Install
npx skillscat add dobeu-tech-eco/dts2-marketplace/feature Install via the SkillsCat registry.
Directory edition: do not run bundled scripts or hooks, a package launcher, or a download piped into a shell. Do not read tokens or credential files from the machine. Carry out the step with Read, Edit, Grep, Glob, and git or gh, and write the files the step names.
Feature — from idea to planned sections, every plan in sync
/dt:feature <description> plans a feature; it does not build it. Building is /dt:run section <#> or /dt:autopilot <#…> afterwards.
1. Pre-check and scope
- Run the run skill's Pre-check (every run command) exactly as written there. An upgrade it starts stops here; the handoff records
Next action: /dt:feature <description>. python3 "${CLAUDE_PLUGIN_ROOT}/scripts/scope-check.py" .→ use the workspace root when it saysworkspace-member. No.harness/end-state.md→ sayNo end state yet; /dt:setup interviews to one.and stop: a feature needs an approved end state to land in.- Read
.harness/end-state.md(Goal, Constraints, Non-goals, Blueprint, Sections, Acceptance criteria, Open questions),.harness/config.yamlpaths.docs,.harness/action-items.md, and every plan-like doc the repo keeps (frompaths.docs, plus any ofPLAN.md,ROADMAP.md,STATUS.md,BRAINSTORM.md,docs/roadmap*,docs/**/plans/*that exist). Record which ones exist; they are the plans to keep in sync. - Conflict check. The feature contradicts a Non-goal or Constraint → quote it and ask once: change the end state (the feature overrides it) or drop the feature. It duplicates an existing component or section → say which and ask: extend that one, or stop.
2. Clarity, then the deep interview only when needed
- Rate the feature as one component (or several, when it plainly spans layers) on the setup skill's Round 4 dimensions (
goal,constraints,success, andcontextfor a brownfield repo), from the description and the repo only. Do not inflate. Write{"mode":"<greenfield|brownfield>","components":[…]}to a temp file outside the repo and runpython3 "${CLAUDE_PLUGIN_ROOT}/scripts/clarity-score.py" <file>. - Threshold:
end_state_thresholdfrom.claude/dts2-harness.local.md, default 80. Start the message withClarity: NN%. - At or above the threshold → go to step 3 (no interview).
- Below it → run the deep interview scoped to this feature, using the setup skill's Part 1 rules verbatim, limited to the new component(s):
- Round 3b. Sections for the feature: each section with
files / area,depends on(existing section numbers allowed),complexity, statustodo; a section with nofiles / areaordepends oncaps clarity exactly as Round 3b says. - Round 4 — Question loop, one question per round at
weakest.component/weakest.dimension, until the threshold, the literalContinue anyway, or 20 rounds. - Round 4b — Skills for the new component only.
- Round 4c. Grill the draft with
/grill-meon the feature's draft (component, Done criteria, Blueprint lines, Sections).
- Round 3b. Sections for the feature: each section with
- Every answer goes into the record; anything unresolved goes to Open questions with the feature's name.
3. Lead writes the plan change
Dispatch dt:lead (seat: sign-off, model: opus) with the feature record, the current end state, .harness/plan-style.md if present, and the list of plan docs. Tell it to return, as one patch, without touching code:
- end-state.md: the component under Topology; its
- [ ]acceptance criteria under Acceptance criteria; Blueprint rows changed or added with status; new rows in## Sectionsnumbered after the last existing one, withdepends onpointing at real section numbers; Constraints, Non-goals, Assumptions and Open questions as the interview settled them; Skills rows for new skills. Existing sections and approved criteria are never renumbered, rewritten or removed. - Each repo plan doc that exists: the feature added in that doc's own format and place (a roadmap entry, a phase task, a status line
planned), never a reformat of the rest. - action-items.md: a Decisions row for each open question, a Secrets row (name only, via
action-items.py <repo> add Secrets NAME) for each new secret the feature needs, a Deploy row for each external setup step. ## Donefor the feature: one checkable outcome per line.
A lead report whose first line isPARTIAL: hit turn cap at <step>is not a patch: do not show it for approval; re-dispatch the lead with a narrower scope or a fresh agent, inside the fix-loop cap.
4. Architecture and agent-friendly passes, then approval
- 5b. Architecture pass. Run
/improve-codebase-architectureagainst the repo with the new sections as the planned change; present its findings as amendments to the patch and askApply these architecture amendments? (y/n/edit). - Show the patch as a diff summary (end state, each plan doc, action items), the new Sections rows, the Done list and the clarity, and ask once:
Add this feature to the plan? Reply "approve", or tell me what to change.On changes, revise with the lead and ask again. Silence means stop. - 5c. Agent-friendly rewrite. After approval, run
/writing-for-agentson the new end-state text only; it changes form, never facts; apply after one yes. - In autopilot, steps 2 and 3's questions are answered by the autopilot consensus gate instead of the user (see the autopilot skill).
5. Land it
- Branch
feature/<slug>fromorigin/<base>(devwhen it exists, else the default branch), write the approved patch, keepstatus: approvedon the end state with a- <date> feature <slug> added: sections <#…>line in.harness/state.md→## Decisions. - Ship it: run
/dt:ship(its pre-check, checks, receipt and PR); the PR's Linked work names the feature slug and the new section numbers. - Refresh the handoff:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-write.py" <repo>. - End with one line naming what to run next:
/dt:run section <first new #>or/dt:autopilot <#,#,…>.
Guardrails
- Planning only: no code, no migrations, no installs beyond the companion skills.
- Never renumber, rewrite or delete approved sections or criteria; only add, or change what the user explicitly approved.
- Questions one at a time, never more than one per message.
- Never print a secret's value; secrets are names only.