speckit-implement

Execute approved spec-kit implementation slices with scoped file changes and validation recording.

95|39|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-implement-liuminxin45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-implement
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-implement
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-implement-liuminxin45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams execute approved implementation slices in a controlled way, so changes stay within scope, evidence is captured, and validation is not skipped.

Core Features & Use Cases

  • Scoped implementation: Patch only the files and source areas allowed by the active slice.
  • Validation discipline: Run the required checks, gate packs, and AI self-acceptance before moving forward.
  • Progress tracking: Record changed files, results, blockers, and next steps in progress.md for recovery and review.
  • Use case: Use this Skill when a spec-kit feature has been approved and you need to complete one slice, prove it works, and hand off cleanly to acceptance.

Quick Start

Apply the approved speckit-implement slice to the current feature, change only the permitted files, run the required validation, and update progress.md with evidence and the next action.

Frequently Asked Questions about speckit-implement

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

FAQPage Schema
How do I execute approved implementation slices while preserving scope and validation discipline?

To execute approved implementation slices safely, apply the active slice to your feature, patch only permitted files, run required gate packs, and record validation results in progress.md before handoff.

What is AI self-acceptance for staged code changes in spec-kit projects?

AI self-acceptance for staged code changes is a validation gate requiring the implementation to pass required checks and prove functionality before moving forward to clean handoff and acceptance.

How do I track implementation progress and blockers during scoped feature development?

Track implementation progress by updating progress.md with changed files, validation results, encountered blockers, and next-stage routing actions to ensure recovery and seamless review.

When do I need to use gate selection for feature implementation workflows?

You need gate selection during feature implementation workflows when an approved spec-kit slice requires staged code changes, ensuring required checks are selected and run before advancing.

Can I write to files outside the allowed write scopes of an active implementation slice?

No, scoped implementation restricts patching to only the files and source areas explicitly allowed by the active slice, ensuring changes stay within the approved boundaries.