ninthhousestudios
UserEngineering methodology skills for Claude Code agents — planning, TDD, diagnosis, architecture
Categories
Indexed Skills (15)
vidhi-domain
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
vidhi-init
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the vidhi skills know this repo's issue tracker (yojana, GitHub, GitLab, or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `vidhi-decompose`, `vidhi-prd`, `vidhi-triage`, `vidhi-diagnose`, `vidhi-tdd`, `vidhi-deepen`, or `vidhi-survey` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
vidhi-brainstorm
Collaborative design exploration. Turns a vague idea into a shared understanding through structured dialogue — one question at a time, 2-3 approaches with trade-offs, incremental design approval. Use before vidhi-domain or vidhi-prd.
vidhi-decompose
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
vidhi-deepen
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
vidhi-diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
vidhi-implement
Execute a yojana task using the appropriate methodology. Takes a task ID, pulls context from yojana, selects the execution method (TDD for features, diagnose for bugs, architecture for refactoring), runs it, and reports results back.
vidhi-onboard
Onboard a codebase into sutra — register the workspace, discover architecture, and propose a .sutra/rules.toml with constraints and convention management. Use when bringing a new project under sutra code intelligence for the first time, or when resetting an existing project's constraint rules from scratch.
vidhi-plan
Plan the implementation of a single yojana task. Explores the codebase, maps files, sequences steps with code sketches, and writes the plan to the task's implementation_plan field. Use after decompose, before implement.
vidhi-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
vidhi-premortem
Stress-test a decomposition before implementation begins. Reviews the full set of slices for coverage gaps, integration risks, dependency problems, and timeline traps. Use after vidhi-decompose, before picking up tasks.
vidhi-release-review
Run a thorough, multi-pass code review of a project at a release or checkpoint moment. Use when the user wants to verify a project is ready to ship, audit a long upgrade arc, or get fresh-eyes review on accumulated changes. Different from vidhi-deepen (forward-looking refactor candidates) and per-task PR review (which uses yojana_context shape="review" directly).
vidhi-review
Review code changes for one or more yojana tasks. Pulls task context, assembles the diff, and either reviews inline or produces a self-contained brief for external models (codex, opencode, etc.). Use for bounded reviews of specific work — not whole-project audits (use vidhi-release-review for those).
vidhi-tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
vidhi-triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.