skills.rest
leanbusqts
leanbusqtsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

implement

Plan, implement, and test scoped code changes with explicit acceptance criteria.

2|Updated Dec 31, 2025
Search Tags:#planning#testing#implement#acceptance-criteria#code-edit#self-review#scoped-change
One-click install
npx skills add https://github.com/leanbusqts/agent47 --skill implement-leanbusqts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/leanbusqts/agent47/tree/main/templates/skills/implement
Command: npx skills add https://github.com/leanbusqts/agent47 --skill implement-leanbusqts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables precise, scoped changes that meet requirements with minimal surface area, reducing blast radius.

Core Features & Use Cases

  • Scope verification: Confirm the exact boundaries of a change before coding.
  • Plan, implement, and test: Plan minimal edits, implement them, and update tests as needed.
  • Self-review: Review changes to ensure correctness and minimize ripple effects.

Quick Start

Example: Use the implement skill to apply a small, well-scoped bug fix or enhancement to a module, ensuring no unrelated behavior is touched and documenting intent.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement scoped code changes with minimal blast radius?▼

Scoped code changes with minimal blast radius require confirming exact boundaries, planning minimal edits, updating tests, and performing a self-review to prevent unintended ripple effects.

What is the best way to plan small code edits based on acceptance criteria?▼

Planning small code edits based on acceptance criteria involves verifying scope, making minimal targeted modifications, adding or updating tests, and reviewing the changes for correctness.

Why do I need to verify scope before applying a bug fix to a module?▼

Verifying scope before applying a bug fix ensures you confirm exact change boundaries, preventing unrelated behavior from being touched and reducing the risk of unintended side effects.

Does disciplined implementation require updating tests for small enhancements?▼

Disciplined implementation requires adding or updating tests for small enhancements to ensure correctness, verify acceptance criteria, and minimize ripple effects during self-review.

When should I not use minimal surface area changes for software engineering?▼

Avoid minimal surface area changes when requirements demand widespread modifications, broad refactoring, or enhancements spanning multiple unrelated modules that exceed strict scope boundaries.

Related Skills

Explore More Software Engineering Skills→
mortenbroesbymortenbroesby
1

spec-driven-development

Define a precise specification with objectives, constraints, and acceptance criteria before coding.

Community
Intermediate
JsplixJsplix

code-review-auto

Orchestrate sequential code review pipelines from design intent to documentation drift detection.

Community
Advanced
multiplex-aimultiplex-ai
2

prompt-optimizer

Analyze draft prompts and map them to ECC workflow components.

Official
Advanced
mmianimmiani
63

kotlin-kmp-refactor-safety

Plan minimal refactor changes that preserve behavior and include targeted tests.

Community
Advanced