implementation-principles

Guides minimal, correct, maintainable code changes that fit existing systems.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/astroville/sprout --skill implementation-principles-astroville
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-principles
Source: https://github.com/astroville/sprout/tree/main/.claude/skills/implementation-principles
Command: npx skills add https://github.com/astroville/sprout --skill implementation-principles-astroville

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineers and AI agents often deliver code that technically passes but misses the spirit of a requirement, silently descopes hard items, or introduces unnecessary abstractions. This Skill provides shared implementation guidance that keeps changes minimal, correct end-to-end, and consistent with existing conventions. ## Core Features & Use Cases - Excellence Bar: Enforces outcome quality on in-scope work, requiring end-to-end working behavior rather than code that merely compiles or passes self-written tests. - Anti-Punt Rules: Defines exactly three options for hard requirements — complete them, halt with a blocker report, or get explicit sign-off — preventing silent descoping. - Minimal-Change Discipline: Directs agents to understand existing code first, reuse utilities and patterns, and avoid opportunistic rewrites or unneeded abstractions. - Use Case: An execution agent implementing a feature spec uses this Skill to stay within the declared scope, surface blockers honestly, and deliver work a senior engineer would approve. ## Quick Start Apply the implementation-principles skill while implementing this feature spec to keep the change minimal, correct, and within scope.

Frequently Asked Questions about implementation-principles

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

FAQPage Schema
How do I keep code changes minimal when implementing a feature spec?▼

Identify the smallest set of files and components that need to change, reuse existing utilities and patterns, and avoid new abstractions without concrete need. Correct means the feature works end-to-end for its intended user, not just that it compiles.

What should an agent do when a requirement is harder than expected?▼

There are three options: complete the item, halt and surface a blocker report naming what was tried and what is needed, or get explicit sign-off to descope. Silent descoping or declaring a stub done is treated as a failure mode.

When should I use implementation-principles versus other coding skills?▼

Use it for nearly all coding tasks that turn requirements or plans into concrete code changes. It pairs with agent-reliability for verification, scope honesty, and persistence rules during delivery.

Does the excellence bar allow expanding scope for a better result?▼

No. The excellence bar raises quality of in-scope work only and is not a license for scope creep. Broader improvements should be surfaced to the delivery lead rather than self-authorized.

What are the limitations of a guidance-only implementation skill?▼

It provides principles and behavioral rules, not executable scripts or automated checks. Enforcement depends on the agent or engineer applying the guidance and self-checking against the excellence bar at the end of each task.