Skip to content

ericrisco/rsc-harness / skills/asdd

Use when a feature or substantial change should go from idea to shipped, verified software and an agent may run it for hours on its own — the ASDD (Agent Spec-Driven Development) dispatcher and front door, in any language. A spec that must prove itself, review inside every task scaled by `rsc risk`, a decision queue for what the agent must not decide alone. Routes constitution -> specify -> clarify -> plan -> tasks -> analyze -> implement (verify + review per task) -> closing -> ship. Successor of `sdd`. NOT a single phase (it dispatches), NOT small authorised changes (that is `ftd`), NOT the workspace harness (that is `harness`).

FileKindSize
SKILL.mdskill md15.2 KB
evals/README.mdmarkdown3.7 KB
evals/cases.yamlconfig8.4 KB
references/model-routing.mdmarkdown11.0 KB

evals/cases.yaml

View on GitHub
skill: asdd

# Cases for the "asdd" dispatcher / front door (ASDD, successor of sdd in 4.0).
# asdd states the SDD method, reads the user's register (technical_level) from
# 02-DOCS/wiki/harness/user-profile.md, and ROUTES to the right phase skill in
# the chain constitution -> specify -> clarify -> plan -> tasks -> analyze ->
# implement -> verify -> review -> ship (debug/worktrees/parallel on demand).
# It does NOT perform a single phase itself and is NOT the workspace harness.

should_trigger:
  - prompt: "I want to build this feature properly, spec-driven, from idea to shipped. Where do I start?"
    why: "Canonical SDD entry: explicit 'spec-driven' + 'idea to shipped' is exactly what the dispatcher routes — it should name the method and hand off to constitution/specify, not start coding."

  - prompt: "Quiero llevar esta idea a producción haciéndolo bien, paso a paso."
    why: "Spanish 'de la idea a producción, haciéndolo bien, paso a paso' is the intent->shipped loop the dispatcher governs; it should place the request on the phase map and route to specify."

  - prompt: "I'm somewhere in the middle of building a feature and I've lost track of which step I'm on. Can you orient me?"
    why: "Non-obvious: no SDD jargon, but 'which step am I on' is precisely the dispatcher's 'which phase are you in' job — it asks the one orienting question (is there a written spec?) and routes."

  - prompt: "Run the full asdd flow on this new authentication requirement."
    why: "Direct request to run the chained flow — the dispatcher owns the flow and routes the first phase; it should not try to do every phase inline itself."

  - prompt: "I have a one-paragraph idea for a notifications feature. Take it all the way to a PR the disciplined way."
    why: "Fuzzy idea + 'all the way to a PR' + 'disciplined' implies the whole chain; the dispatcher should start at specify and explain the gates rather than jumping to implementation."

  - prompt: "Before we touch code, I want a proper process: decide what and why, write it down, then build. Set that up."
    why: "Describes SDD by definition (what/why before how, write it down) without the acronym — a deliberately non-obvious trigger the dispatcher must claim and route from."

  - prompt: "What's the right order to do this feature in, and which phase skill handles each part?"
    why: "Asks for the phase map and the per-phase ownership — the dispatcher's core deliverable; it should produce the chain and the routing rule."

  - prompt: "We have an existing repo and no SDD config yet. Start the SDD flow properly before we write a spec."
    why: "The dispatcher should notice the missing runtime calibration and route to sdd-init before specify on non-trivial work."

  - prompt: "I want planning and review to run on the strongest model but implementation on a cheaper one. Set that up for our SDD flow."
    why: "Per-phase model routing is an SDD concern the dispatcher owns: it should name the tier system (heavy/balanced/light), point at the models block in 02-DOCS/wiki/sdd/config.yaml written by sdd-init, and note it is opt-in — not start coding."

should_not_trigger:
  - prompt: "Write the spec for the new export-to-CSV feature."
    route_to: "specify"
    why: "A concrete request to PRODUCE the spec is a single phase the dispatcher hands off — specify owns writing specs and asking the focused questions. sdd only routes."

  - prompt: "Set this repo's non-negotiable engineering principles and stack canon."
    route_to: "constitution"
    why: "Capturing project-wide non-negotiables is the constitution phase, which runs once per project. The dispatcher would point here, but the work itself belongs to the constitution skill."

  - prompt: "All the code is written and tests pass — open the PR and merge it."
    route_to: "ship"
    why: "Closing the branch (PR/merge/cleanup, Eric-only authorship) is the ship phase. No dispatching needed; this is squarely ship's job."

  - prompt: "Audita mi proyecto y monta el 01-TOOLS y el 02-DOCS."
    route_to: "harness"
    why: "Workspace control plane (01-TOOLS/02-DOCS scaffolding/audit) is the harness, not the SDD engineering flow. sdd writes its artifacts INTO 02-DOCS but does not build the harness."

  - prompt: "There's a failing test and I don't know why — help me find the root cause before I change anything."
    route_to: "debug"
    why: "Root-cause diagnosis of a specific failure is the on-demand debug phase. The dispatcher references it, but a direct 'find the root cause' request goes straight to debug, not through routing."

  - prompt: "Scaffold a new Next.js app with the App Router and Tailwind."
    route_to: "nextjs"
    why: "A concrete stack build with a named framework is the nextjs stack skill. sdd is process, not stack; it would defer build specifics to nextjs rather than fire itself."

capability:
  - scenario: "A developer whose profile says technical_level: technical says: 'I've got a rough idea for a feature and I want to build it the spec-driven way, end to end. Where do I begin?' Show how the dispatcher opens the engagement."
    must_include:
      - "States the SDD method in brief: decide what & why before how, write it down, each artifact gates the next ('the artifact is the contract')"
      - "Reads (or notes it should read) technical_level from 02-DOCS/wiki/harness/user-profile.md and, being technical, uses technical terms directly with a one-line why per step rather than long explanations or analogies"
      - "Presents the chained phase map: sdd-init -> constitution -> proposal? -> specify -> clarify -> plan -> tasks -> analyze -> implement -> verify -> review -> ship -> archive, with debug/worktrees/parallel on demand"
      - "Includes sdd-init as step zero when 02-DOCS/wiki/sdd/config.yaml is missing, and explains that it detects test commands, strict TDD and .rsc/skill-registry.json"
      - "Applies the invoke rule: a fuzzy idea with no spec on disk routes to specify (and notes constitution runs once per project if not yet present)"
      - "Does NOT itself write the spec or start coding — it hands off to the specify phase skill (../specify/SKILL.md)"
      - "Notes that artifacts will be written under 02-DOCS/wiki/sdd/ (specs/, plans/, decisions.md) and indexed in 02-DOCS/wiki/index.md (never the root CLAUDE.md)"
      - "Mentions standard result envelopes with status, artifact, next_recommended, risk, skill_resolution and evidence"
      - "Defers concrete stack tooling (test runner, build, framework idioms) to the relevant stack skill rather than prescribing it here"

  - scenario: "A user says: 'It's a tiny copy change in the footer — do I really have to run this whole spec/plan/tasks ceremony?' Show how the dispatcher handles the skip case honestly."
    must_include:
      - "Applies the skip rule: a one-line, low-risk change does not need the full chain, and says so explicitly"
      - "Still requires a verification step after the change (the method serves shipping, not ceremony, but evidence before claiming done remains)"
      - "Does not abandon the method for genuinely risky work — distinguishes trivial from non-trivial and is honest about which this is"
      - "If git authorship comes up, notes ship enforces Eric-only authorship (no Co-Authored-By Claude, no generated-with footer)"

  - scenario: "A user asks: 'Can SDD use a cheaper model for the boring phases and the strong one for the hard ones? How do I turn that on?' Show how the dispatcher explains per-phase model routing."
    must_include:
      - "Names the three tiers — heavy (deep reasoning), balanced (execution), light (mechanical) — and that each phase has a default tier"
      - "States the default quality-biased mapping: heavy on constitution/plan/analyze/review/debug, balanced on specify/clarify/tasks/implement/verify, light on ship/worktrees/sdd-init"
      - "Says routing is OFF by default (models.enabled:false) and lives in the models block of 02-DOCS/wiki/sdd/config.yaml, written by sdd-init; turning it on is the user's choice"
      - "Explains the two application layers: programmatic (dispatching Task/parallel subagents on the tier's model, e.g. Claude Code) and advisory (announcing the recommended switch at the phase boundary, in one line)"
      - "Is honest about limits: never switches unasked, never claims a model switch an assistant cannot make, and skips routing on trivial one-line changes"
      - "Points to references/model-routing.md for the full protocol, per-assistant mechanism, and provider→model table rather than inventing model names inline"
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall