Skip to content

ericrisco/rsc-harness / skills/analyze

analyze

Verified

Use when constitution, spec, plan and tasks all exist and you want them cross-read against each other before any code is written — the rsc-sdd pre-implementation gate. Reports coverage gaps, contradictions, duplication, ambiguity and scope drift; edits nothing. NOT the task breakdown (that is `tasks`), NOT the coding (that is `implement`), NOT the post-code test gate (that is `verify`), NOT resolving ambiguity (that is `clarify`).

FileKindSize
SKILL.mdskill md10.8 KB
evals/README.mdmarkdown3.8 KB
evals/cases.yamlconfig6.4 KB

evals/cases.yaml

View on GitHub
skill: analyze

# Prompts that MUST load the `analyze` skill. `analyze` is the rsc-sdd
# pre-implementation GATE: it cross-reads constitution vs spec vs plan vs tasks
# and REPORTS gaps, contradictions, duplication, ambiguity and scope drift. It
# never edits the artifacts and never writes code — the user resolves each
# finding. Several prompts deliberately avoid the word "analyze" to test that
# the intent (a consistency cross-check before coding) is what triggers.
should_trigger:
  - prompt: "The spec, plan and task list are all written — before I start coding, can you check they actually agree with each other?"
    why: "Cross-reading spec/plan/tasks for agreement right before implementation is the exact job of the pre-implementation gate."

  - prompt: "Did we miss any requirement? I want to know which spec requirements have no task behind them."
    why: "Requirement coverage (spec -> plan -> tasks) and surfacing GAPs is analysis #2; the user is asking for the coverage map without naming the skill."

  - prompt: "The plan mentions a Redis cache and a webhook handler that I don't remember being in the spec — is that scope creep?"
    why: "Plan/task work that satisfies no spec requirement is DRIFT — analysis #3; this is the backward-mapping check phrased as 'scope creep'."

  - prompt: "Run the consistency gate over the SDD artifacts for the checkout feature."
    why: "Explicit request for the consistency gate across the SDD artifacts; the core trigger for this phase."

  - prompt: "Our constitution says Postgres only, but I think the plan picked a different database somewhere — can you cross-check before we build?"
    why: "Constitution compliance (analysis #1) plus contradiction detection between constitution and plan, explicitly before building."

  - prompt: "Sanity-check the spec against the plan and tasks for me — I don't want to find contradictions halfway through implementing."
    why: "Pre-implementation contradiction detection across the artifacts is the gate's purpose; 'halfway through implementing' is the cost analyze exists to avoid."

  - prompt: "Before implement, is everything aligned? Give me a coverage map of requirements to tasks."
    why: "Asking for alignment plus a requirement-to-task coverage map immediately before the implement phase is precisely the analyze hand-off."

# NEAR-MISS prompts that must NOT load `analyze`. Each routes to the genuinely
# correct sibling that exists in this repo. The recurring trap: anything that
# RESOLVES, BUILDS, or RUNS rather than reports, and anything that inspects code
# rather than the SDD planning artifacts.
should_not_trigger:
  - prompt: "The login test is failing with a 500 and I can't tell why — help me find the root cause."
    route_to: "security-audit"
    why: "A failing test / runtime fault is root-cause debugging on code, not a planning-artifact cross-check; analyze never opens source files. (Routes to the nearest existing repo skill for the auth fault.)"

  - prompt: "Run the lint, type-check and test suite and tell me if the FastAPI service is ready to ship."
    route_to: "fastapi"
    why: "Running lint/types/tests on built code is the post-implementation verification gate via the stack skill — analyze is pre-implementation and runs nothing."

  - prompt: "Write the technical implementation plan for the payments feature from this spec."
    route_to: "fastapi"
    why: "Authoring the plan/architecture is plan-phase work delegated to the stack skill; analyze checks an existing plan, it does not write one."

  - prompt: "Review this pull request diff for correctness bugs and cleanups."
    route_to: "security-audit"
    why: "Adversarial review of a code diff is code review, not a constitution/spec/plan/tasks consistency report on planning artifacts."

  - prompt: "Audit my workspace and set up 01-TOOLS and 02-DOCS with a Knowledge map."
    route_to: "harness"
    why: "Bootstrapping the workspace control plane is the harness's job; analyze only reads the SDD artifacts the harness's 02-DOCS layer happens to store."

  - prompt: "Profile why the Postgres query in the dashboard is slow and propose an index."
    route_to: "postgresdb"
    why: "Query performance and indexing is database engineering on real code/SQL, not a pre-implementation artifact cross-check."

# Concrete tasks the skill should guide, with a rubric to grade WITH vs WITHOUT
# the skill loaded. A correct skill-guided answer reports and routes; an
# ungrounded answer typically starts editing artifacts or jumps to coding.
capability:
  - scenario: "I have constitution.md, a spec, a plan and a task list under 02-DOCS/wiki/sdd/ for a 'team invites' feature. The constitution says 'Postgres only, every endpoint rate-limited'. The spec requires email invites with a 5/min rate limit and invite expiry after 7 days. The plan adds a Redis-backed cache nobody asked for and is silent on rate limiting. The tasks cover sending invites and expiry but have no task for rate limiting and no done-check on the expiry task. Run the gate."
    must_include:
      - "Reports only and resolves nothing: explicitly does NOT edit the spec/plan/tasks and writes no code; hands each finding back to the user to resolve."
      - "Reads technical_level from 02-DOCS/wiki/harness/user-profile.md and writes the report in that register (or notes no profile and uses analogies), with every finding in one line."
      - "Runs all six analyses (constitution compliance, coverage, scope drift, contradiction, duplication, ambiguity), not just coverage."
      - "Flags the missing rate-limit task as a coverage GAP and as a CONSTITUTION violation (constitution requires every endpoint rate-limited) — marks it CRITICAL/HIGH and routes it to the tasks/plan phase."
      - "Flags the Redis cache as scope DRIFT (no spec requirement behind it) and notes the resolution is the user's call: cut it or amend the spec."
      - "Flags the expiry task's missing done-check as AMBIGUOUS and routes it to the tasks phase; flags any vague requirement to clarify."
      - "Builds a requirement-coverage map (REQ -> plan section -> task -> status) marking covered / GAP / DRIFT / AMBIGUOUS."
      - "Emits a verdict line (GATE: BLOCKED here, with CRITICAL/HIGH counts) and writes the report to 02-DOCS/wiki/sdd/analysis/<slug>.md indexed in the Knowledge map."
      - "Ends by pointing to the next phase: route the blocking findings back to their owning phases, resolve, re-run analyze; only on PASS proceed to implement."
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall