skills.rest
Grimblaz
GrimblazCOMMUNITY
Explore all skills by this author →
GitHub

implementation-discipline

Implement small requirement-driven changes while delegating to existing components.

3|Updated Dec 7, 2025
Search Tags:#workflow#planning#refactoring#implementation#delegation#quality#code
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill implementation-discipline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-discipline
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/implementation-discipline
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill implementation-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Minimal implementation workflow helps teams land small, requirement-driven changes without duplicating existing logic, ensuring compliance with design constraints and smooth handoff.

Core Features & Use Cases

  • Apply requirements-first discipline to every change.
  • Ensure small, delegating updates rather than broad rewrites.
  • Validate changes against the plan and architecture before integration.

Quick Start

Identify the smallest required change that satisfies the plan and delegate tasks to existing components where appropriate.

Frequently Asked Questions about implementation-discipline

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

FAQPage Schema
How do I implement small code changes without duplicating existing logic?▼

To implement small code changes without duplicating logic, identify the smallest required modification that satisfies your plan and delegate tasks to existing components. This enforces minimal updates and prevents broad rewrites.

What is a plan-driven implementation workflow for software engineering?▼

A plan-driven implementation workflow applies requirements-first discipline to code changes by enforcing minimal modifications, aligning updates with design constraints, and validating delegation boundaries before integration.

How do I validate delegation boundaries across modules during a refactor?▼

Validate delegation boundaries across modules by enforcing explicit verification steps before integration, ensuring incremental changes align with architectural constraints and delegate correctly to existing components.

When should I use a minimal implementation workflow instead of a broad rewrite?▼

Use a minimal implementation workflow when planning bounded feature slices or performing incremental changes, ensuring small delegating updates rather than broad rewrites to maintain design compliance.

Does a requirements-first approach help with incremental refactoring?▼

A requirements-first approach helps incremental refactoring by applying strict alignment with plan and architecture constraints, validating every small change against the original design before integration.

Related Skills

Explore More Software Engineering Skills→
HAR5HA-7663HAR5HA-7663

shape

Plan feature UX and UI through a structured discovery interview.

Community
Intermediate
YokhanYokhan

add-feature

Scaffold a vertical slice feature under src/features/[name]/ with standard files.

Community
Intermediate
1ambda1ambda
2

Integration Finder

Identify and suggest integrations between new modules and existing codebase components.

Community
Intermediate
spontus-reachspontus-reach
1

improve-codebase-architecture

Identify shallow modules and propose higher-depth refactors with interface-level test surfaces.

Official
Intermediate