skills.rest
maestria-co
maestria-coOFFICIAL
Explore all skills by this author →
GitHub

implementing-features

Implement features, bug fixes, or refactors from a clear specification.

Updated Mar 2, 2026
Search Tags:#testing#refactor#code-quality#features#bug-fix#acceptance-criteria#implementing
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill implementing-features-maestria-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementing-features
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/implementing-features
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill implementing-features-maestria-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements a feature, bug fix, or refactor from a clear specification to ensure changes are scoped, minimal, and verifiable.

Core Features & Use Cases

  • Guided, repeatable execution steps that restate acceptance criteria, identify scope, implement minimally, verify results, and perform self-review.
  • Use cases include implementing a new feature from a spec, applying a bug fix with explicit criteria, or refactoring with a defined goal, while preserving existing patterns.
  • Real-world example: transform a vague task into a concrete, testable change and verify via the project’s build pipeline.

Quick Start

Review the task specification and acceptance criteria, determine scope, implement minimally, and verify by running the build.

Frequently Asked Questions about implementing-features

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

FAQPage Schema
How do I implement a feature from a spec without breaking existing code patterns?▼

Implement features from a spec by restating acceptance criteria, identifying scope, coding minimally, and verifying results. This ensures changes remain scoped, testable, and aligned with existing code patterns.

What is the best way to turn vague software tasks into verifiable changes?▼

Transform vague tasks into verifiable changes by applying a structured process that defines explicit acceptance criteria and a well-scoped change boundary. You then implement minimally and validate through the project's build pipeline.

How do I plan a code refactor with a defined goal?▼

Plan a code refactor by first identifying the explicit acceptance criteria and change boundary. Execute the refactor minimally to preserve existing patterns, then verify the results by running the project's build.

Does applying a bug fix require explicit acceptance criteria?▼

Yes, applying a bug fix requires explicit acceptance criteria to ensure the change is minimal and verifiable. Restating these criteria guides the implementation and confirms the fix satisfies the required behavior.

When should I not use a minimal implementation approach for software changes?▼

Avoid minimal implementation when a task lacks a clear specification or well-scoped change boundary. Without explicit acceptance criteria, the structured process of planning, coding, testing, and validation cannot effectively verify results.

Related Skills

Explore More Software Engineering Skills→
dreamingechoesdreamingechoes
2

spec-driven-development

Draft structured project specs covering requirements, design, testing, and acceptance criteria.

Community
Advanced
GigaFydeGigaFyde

project-orchestrator:implementer

Automate feature implementation workflows in multifile monorepos by reading living state docs, running tests, and reporting results.

Community
Advanced
viktorbezdekviktorbezdek
10

moai-workflow-testing

Automate end-to-end development workflows integrating testing, debugging, profiling, and code review.

Community
Advanced
jimmi2051jimmi2051

ralplan

Convert vague execution prompts into auditable consensus plans with acceptance criteria.

Community
Advanced