From hatch3r
Guides end-to-end feature implementation workflow as vertical slices covering data model, domain logic, API, and UI. Use for new features or feature request issues.
npx claudepluginhub hatch3r/hatch3rThis skill uses the workspace's default tool permissions.
> **Note:** Commands below use `npm` as an example. Substitute with your project's package manager (`yarn`, `pnpm`, `bun`) or build tool when your project uses a different package manager.
Guides end-to-end feature implementation: requirements analysis, task planning, TDD coding, full testing, self-review, and commit/PR. Use for feature specs or issues.
Guides feature or multi-file implementation with structured workflow: clarify requirements, select personas, implement safely, add tests, and validate.
Guides feature development systematically: explore codebase with agents, clarify requirements, design architecture, implement, test, and review.
Share bugs, ideas, or general feedback.
Note: Commands below use
npmas an example. Substitute with your project's package manager (yarn,pnpm,bun) or build tool when your project uses a different package manager.
Task Progress:
- [ ] Step 1: Read the issue and all relevant specs
- [ ] Step 2: Produce an implementation plan
- [ ] Step 2b: Test-first approach (TDD alternative — optional)
- [ ] Step 3: Implement the vertical slice
- [ ] Step 4: Write tests (unit, integration, security, E2E)
- [ ] Step 5: Verify quality gates
- [ ] Step 5b: Browser verification (if UI)
- [ ] Step 6: Open PR
similar-implementation researcher output, read the reference implementations and their extracted conventions. These define the patterns this feature should follow (file structure, state management, error handling, data fetching, test structure, component composition).requirements-elicitation answers, read them to understand explicit user decisions on ambiguities (data shape, error behavior, UI states, security model, etc.). Do not guess when explicit answers are available.Before coding, output:
similar-implementation output), with divergences noted and justified. If no reference was provided, note "no reference — using best judgment from codebase conventions."When acceptance criteria are specific and testable, write tests BEFORE implementing:
Prefer TDD when:
Use standard flow (implement → test) when:
npm run lint && npm run typecheck && npm run test
Skip this step if the feature has no user-facing UI changes.
Use the project's PR template. Include:
Note: When this skill is invoked via the orchestration pipeline (board-pickup or workflow commands), skip this section — the orchestrator handles agent delegation in Phases 3 and 4.
You MUST spawn these agents via the Task tool (subagent_type: "generalPurpose") at the appropriate points:
hatch3r-researcher — MUST spawn before implementation with modes codebase-impact, feature-design, architecture. For Tier 2+ tasks (per hatch3r-deep-context), also include similar-implementation and requirements-elicitation. Skip only for trivially simple features (risk:low AND priority:p3).hatch3r-implementer — MUST spawn one per sub-issue when the feature is decomposed into multiple tasks. Each implementer receives its own sub-issue context, plus reference conventions and resolved requirements from the researcher output.hatch3r-reviewer — MUST spawn after implementation for code review before PR creation.hatch3r-qa-validation — use this skill for end-to-end verification of the implemented feature