implementing-feature

Plan and implement features phase-by-phase with linting and user authorization before commits.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/fascari/ai-config --skill implementing-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-feature
Source: https://github.com/fascari/ai-config/tree/main/skills/implementing-feature
Command: npx skills add https://github.com/fascari/ai-config --skill implementing-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex feature implementation often suffers from scope drift, unvalidated changes, and unsafe commits. This Skill provides a disciplined, phase-by-phase workflow with per-phase validation and explicit user authorization to ensure safe, incremental delivery.

Core Features & Use Cases

  • Phase-driven plan execution: coordinates plan reading, per-phase checks, and gated commits.
  • Linting and test integration: enforces project coding rules before changes are accepted.
  • Use Case: When implementing a new feature, orchestrating-tasks delegates implementation tasks and ensures each phase passes quality gates before moving to the next.

Quick Start

Start phased implementation by initiating the orchestrating-tasks flow with the current plan.

Frequently Asked Questions about implementing-feature

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

FAQPage Schema
How do I prevent scope drift when implementing complex features?

Safe feature implementation uses a phase-by-phase workflow with built-in validation gates. Each phase requires passing automated checks and linting before advancing, ensuring incremental changes are validated and explicitly authorized.

Can I enforce project coding rules and linting before committing changes?

Yes, enforcing project coding rules before committing changes is handled via per-phase linting integration. The implementation workflow runs automated checks against defined rules, only accepting phase changes when validation passes.

How do I set up a phased implementation plan for a new feature?

Setting up a phased implementation plan requires defining a structured plan with distinct phases. The workflow reads this plan to coordinate execution, applying strict coding rules and per-phase validation checks.

What is the best way to ensure safe, incremental commits during bug fixes?

Safe incremental commits require explicit user authorization before finalizing changes. The workflow uses a separate committing-changes skill to handle production commits only after each phase passes validation.

Does feature implementation require a separate skill to finalize commits?

Yes, finalizing production commits requires a separate committing-changes skill. The implementation workflow focuses on phased execution and validation, delegating actual commit finalization to ensure safe delivery.