TheSoftwareHouse

Writes TSH's implementation plan as a committed file at specifications/<task-id>/<task-name>.plan.md: phased tasks that each name their files and a verifiable Definition of Done, technical context persisted for implementers, explicit parallel groups. Use when…

Finds and fixes the root cause of a bug: pins the symptom, reproduces it, secures a failing test — existing, corrected or new — narrows to the cause with evidence rather than plausibility, measures how far the fix reaches before applying it minimally, and…

Implements a feature, ticket, or plan end to end from the main conversation: confirms a plan file exists, delegates each task to implementer subagents — in parallel where the plan allows — gates on their reports, then closes with the plan's final verification…

Creates a new workspace in a project's `<project>-context` knowledge base — the folder, its README index, its CLAUDE.md with exactly one named owner, and its row in the area map, all in one change. Use when a new layer or area of such a project needs its own…

Scaffolds a project's context repository — a knowledge base with named owners per project and delivery layer, one folder for all decision records, a link-and-table quality gate, and a Claude Code marketplace for the project's own extensions — then enables it,…

Reads a project's knowledge base — the `<project>-context` repository beside its code: scope, accepted decisions, vocabulary, who owns what — before work that depends on it, and cites the document behind every project fact. Use when a task in a repository of…

Finds and repairs broken references in a project's `<project>-context` knowledge base — relative links that no longer resolve, filenames that are not kebab-case, and markdown tables that render wrongly — using the repository's own checker scripts. Use when…

Adds or updates a document in a project's knowledge base — the `<project>-context` repository — picking the owning workspace, applying the state-of-today rule, updating the workspace index, and naming the owner who reviews it. Use when something learned,…

Owns the canonical implementation orchestration workflow for feature implementation, including planning readiness, Human approval gating, delegated execution routing, todo control, and review gates. Use when handling implementation orchestration,…

Creates implementation plan documents (*.plan.md) that break a designed solution into phases and verifiable tasks. Owns the plan template (plan.example.md), plan structure rules, and task definition-of-done rules. Use when authoring, revising, or structuring…

Create custom prompt files (.prompt.md) for GitHub Copilot in VS Code. Provides templates, guidelines, and a structured process for building prompt files that trigger specific workflows routed to the right custom agent, with model selection inferred from that…

UI verification criteria, structure checklists, severity definitions, and tolerance rules for comparing implementations against Figma designs. Use for verifying UI matches design, understanding what to check, and determining acceptable differences.

Automate browser interactions, test web pages and work with Playwright tests.

Frontend component patterns, composition, design token integration, barrel file organization, error handling, and Figma-to-code workflow. Use when implementing UI components, translating Figma designs into code, managing component state, or integrating with a…

Authors and updates repository documentation — README, CHANGELOG, in-repo `/docs`, and the published documentation site. Covers documentation structure, documentation-site build expectations, and the write-vs-review boundary. Use when creating or editing…

Design the architecture to solve a given task: analyse the codebase, resolve ambiguities, and propose a solution following best practices and standards. Produces the solution design that tsh-creating-implementation-plans turns into an implementation plan.

Scaffold new Next.js API route handlers with auth guards, Zod validation, error handling, and integration tests. Use when creating new API endpoints, adding CRUD operations, or building route handlers.

Scaffold background jobs with node-cron scheduling, pessimistic locking via acquireJobLock, and instrumentation.ts registration. Use when creating scheduled jobs, adding cron tasks, or implementing background processing.

Scaffold TypeORM EntitySchema definitions with TypeScript interfaces, database migrations, and Zod validation schemas. Use when creating new database entities, adding tables, or modifying existing entity structures.

Write Playwright E2E tests with direct DB seeding, API-based login, accessible selectors, and dual-config awareness. Use when creating end-to-end tests, testing user flows, or verifying UI behavior.

Write Vitest integration tests against a real PostgreSQL test database with proper mock setup, seed functions, and assertion patterns. Use when creating tests for API routes, lib modules, or database operations.

Builds and extends the backend-for-frontend that fronts the engine's public onboarding API — the NestJS service in packages/demo-bff: its engine client, the start/state/submit loop, document-upload reservation, the onboarding.state_changed webhook receiver,…

Creates and revises the engine's JSON onboarding workflow definitions under workflows/ — choosing the scope, picking step types, wiring ports, binding connectors, validating and compiling without booting the stack, and publishing a change as a new version.…