implement-change
Implement Change
Execute an implementation plan phase by phase, producing working code with verification at each step.
Design Philosophy
While implementing, consult references/software-design-philosophy.md for code-level design principles. Watch for red flags: shallow modules, information leakage, pass-through methods, temporal decomposition.
Principles
- Understand before coding — read all relevant files thoroughly first
- Phase by phase — complete one phase before starting the next
- Verify as you go — run checks after each phase, fix issues before proceeding
- Adapt to reality — plans are guides, not rigid scripts; handle mismatches thoughtfully
- Track progress — keep todos updated, check off items as completed
- Sub-agents for exploration, not execution — dispatch sub-agents to research codebase patterns or read multiple files in parallel before coding. Do not delegate code changes to sub-agents — implement directly. Fan out multiple sub-agents in one turn when gathering independent context (e.g., reading tests + reading related modules).
Input
More from teambrilliant/dev-skills
implementation-planning
>-
11product-thinker
>-
10shaping-work
Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea that needs to become a concrete work definition — feature requests, bug reports, PRDs, customer feedback, Slack threads, stakeholder asks, or vague "we should do X" statements. Trigger phrases include "shape this", "scope this", "write a PRD", "define this work", "turn this into a ticket", "flesh this out", "spec this out", "what should we build for X", "I have an idea for...", or any rough input that needs structure before implementation can begin.
9qa-test
Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser", "verify the feature", "qa test", "browser test", or after completing an /implement-change to verify acceptance criteria in a real browser. Opens Chrome via MCP, exercises each acceptance criterion, verifies via DOM snapshots, and reports pass/fail. The "closer" for every implementation — proof it works, not just that tests pass.
8systems-decomposition
Break down complex products, features, or systems into fundamental primitives and building blocks. Use when someone says "break down X", "decompose this", "what are the primitives for Y", "building blocks of Z", or needs to understand a complex system from first principles. Outputs human-readable lists with ASCII diagrams showing relationships.
7product-discovery
>-
3