usk6666/yorishiro-proxy / .claude/skills/implement
implement
VerifiedLoad a Linear Issue and execute the full workflow from branch creation to implementation, testing, commit, and PR creation
/implement
An end-to-end workflow skill for implementing a Linear Issue through to PR creation.
Arguments
/implement <Issue ID>— Implement the specified Issue (e.g.,/implement USK-12)
Steps
- Load Issue: Fetch Issue details with
mcp__linear-server__get_issue - Update Issue status: Update status to "In Progress"
- Create branch: Generate an appropriate branch name from the Issue
- feat:
feat/<id>-<short-desc> - fix:
fix/<id>-<short-desc> - other:
chore/<id>-<short-desc>
- feat:
- Design review (mandatory for any Issue that introduces a new public type, modifies an interface, or touches more than one package; skip for docstring-only / test-only / single-call-site fixes — note the skip reason in the user-facing plan): launch the design-reviewer agent. See "Design Review Invocation" below.
- Present plan to user: Issue summary, file actions (new / modified / untouched), key resolved decisions from the design review, the Test Plan (the failing tests that will be written first), deferred items, unresolved questions. Get user confirmation before implementing. For trivial Issues that skipped Step 4, present a one-paragraph plan that still names the failing test(s) to write first, or the TDD exemption that applies.
- Red — write failing tests first: Follow "TDD Workflow" Phase 1 in
.claude/agents/implementer.md(it is the single source for the rules and exemptions). Write the tests plus compile-only scaffolding, run them withmake test-pkg PKG=<pkg> RUN=<regexp>, confirm each fails on its assertion (not a compile error orno tests to run), and commit them alone astest(<scope>): add failing tests for <Issue ID>. Keep the--- FAIL:lines for the PR body. - Green, then refactor: Implement until the Phase 1 tests pass, without weakening any Phase 1 assertion (implementer.md Phase 2), then refactor.
- Verify:
- Auto-format with
gofmt -w . make lint(gofmt check + golangci-lint: govet / staticcheck / unused / ineffassign / gocyclo)make buildmake test
- Auto-format with
- Commit: Commit in Conventional Commits format, as a separate commit after the Step 6 red commit (do not amend or squash them together)
- Include
Refs: <Issue ID>in the commit message footer
- Include
- Push: Push to remote with
git push -u origin <branch-name> - Create PR:
- Review changes with
git diff main...HEAD - PR title in Conventional Commits format (e.g.,
feat(protocol): add HTTP handler) - PR body follows the template below
- Create PR with
gh pr create
- Review changes with
- Update Issue status: Update status to "In Review"
- Report results: Display implementation summary + PR URL
Design Review Invocation
Read .claude/agents/design-reviewer.md and replace the placeholders before launching:
| Placeholder | Value |
|---|---|
{{SCOPE_DESCRIPTION}} | Issue title + description + tentative file action list (new / modified) inferred from the Issue |
{{SPEC_REFERENCES}} | Paths to relevant spec/design docs (docs/rfc/envelope.md for data path; protocol-specific RFCs; docs/rfc/plugin-migration.md for plugin work). Cite specific sections, not whole files. |
{{PACKAGES_TO_SURVEY}} | Packages the new code creates, modifies, or depends on |
{{COMPLETED_CONTEXT}} | One-paragraph summary of relevant existing public surface this Issue will integrate with (types/functions, not the whole architecture) |
{{PRODUCT_IDENTITY}} | Read from .claude/skills/review-gate/SKILL.md Phase 1-4 "Product context" block — single source of truth |
{{PRINCIPLES}} | The MITM Implementation Principles from CLAUDE.md (the 6-item list). Quote verbatim. |
Launch:
Agent(
description="Design review: <Issue ID>",
subagent_type="general-purpose",
prompt=<composed prompt>
)
Process the result:
- All resolved → fold the resolved decisions table into the Step 5 plan
- Unresolved items exist → present only the unresolved questions to the user in Step 5 with the agent's proposed answers and trade-offs. Do not ask the user about resolved questions.
- Fitness check FAIL → stop and report. Do not proceed to Step 5 until the scope is adjusted.
PR Body Template
## Summary
- <bulleted list of changes>
## Test plan
- [ ] Test items
## TDD evidence
- Red commit: <sha> (or: exempt — <reason>)
- Failing output at the red commit:
--- FAIL: TestX_Scenario ...
- Phase 1 test changes after the red commit: none (or: <commit> — <why>)
Resolves <Issue ID>
Linear: https://linear.app/usk6666/issue/<Issue ID>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Notes
- If build or tests fail, fix the issues before re-running
- Determine implementation scope from Issue labels and description
- The design review in Step 4 already serves as the implementation plan for non-trivial Issues — Step 5 just relays it to the user
- Since build/test verification was done in Step 8, do not re-run when creating the PR
- If PR creation fails, guide the user to manually run
/pr - Before completing implementation, verify that the feature is accessible from the config file (no missing config struct, validation, or init function changes)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |