implementation-guidance

GodSpeedAI's avatarfrom GodSpeedAI

Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026
[Code Generation]

When & Why to Use This Skill

The Implementation Guidance skill is a specialized Claude agent tool designed to bridge the gap between high-level planning and high-quality code execution. It ensures that every code change adheres to strict architectural standards, follows Test-Driven Development (TDD) principles, and maintains project integrity. By providing a structured workflow for incremental implementation and automated validation, this skill helps developers produce maintainable, production-ready code while minimizing technical debt.

Use Cases

  • Step-by-Step Feature Implementation: Transforming a single milestone from a PLAN.md file into functional code while ensuring all acceptance criteria are met.
  • Architectural Compliance: Automatically reviewing ARCHITECTURE.md and CONTRIBUTING.md during the coding process to prevent violations of design patterns or security policies.
  • Automated TDD Workflow: Guiding the creation of unit and integration tests before production code is written to ensure robust software behavior.
  • Incremental Code Refactoring: Managing small, focused commits to avoid large, complex diffs, making code reviews more efficient and reducing regression risks.
  • Quality Assurance & Validation: Executing linting, static analysis, and custom validation tasks immediately after coding to ensure immediate fix of issues.
nameimplementation-guidance
description'Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.'
idce.skill.implementation-guidance
tags[execution, testing, validation]
files[]
concepts[small-diffs]
tools[toolset:write]
artifacts[ce.prompt.implement-step]
actions[apply-changes]

Implementation Guidance Skill

This skill helps you turn a single plan step into code changes while following TDD and maintaining architectural integrity.

Steps

  1. Select a plan slice. Identify the next unimplemented milestone or task from PLAN.md. Summarise its objective, inputs, outputs and acceptance criteria.

  2. Review constraints. Load ARCHITECTURE.md and CONTRIBUTING.md to understand any constraints (e.g. design patterns, layer boundaries, security policies). Ensure your implementation will not violate them.

  3. Write tests first. Before writing production code, design unit and integration tests that express the desired behaviour. Use the testing strategy guidelines and harness appropriate frameworks.

  4. Implement incrementally. Write small, focused commits that satisfy one test at a time. Avoid large diffs. Document significant decisions or deviations in an ADR if necessary.

  5. Run validation and linting. After coding, execute the validation task (Context Kit: Validate) and any language-specific linters or static analysis tools. Fix issues immediately.

  6. Summarise changes. Prepare a concise summary of what was changed, which files were touched and how the acceptance criteria were met. Provide links to relevant docs or ADRs.

  7. Handoff for review. Once the step is complete and validated, hand off to the reviewer agent or trigger the review-changes prompt for quality assurance.

By following this process you produce maintainable code that is easy to review and less likely to introduce regressions or technical debt.