implement-with-feedback

Convert a formal plan into local git-centric sprint execution with tracker updates.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Xalior/agent-skills --skill implement-with-feedback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-with-feedback
Source: https://github.com/Xalior/agent-skills/tree/main/implement-with-feedback
Command: npx skills add https://github.com/Xalior/agent-skills --skill implement-with-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consolidates plan-to-implementation work into a disciplined, local, git-centric workflow that turns a plan document into a sequence of sprints with a living tracker.

Core Features & Use Cases

  • Preflight-driven setup: locate the plan, verify a clean working tree, create a feature-style branch, and run baseline checks without pushing.
  • Tracker-driven sprint execution: translate plan phases into refined sprints, update a living tracker, and commit incrementally.
  • Local-first workflow: all commits stay on disk until you explicitly push or open a PR, preserving a safe development loop.
  • Optional tracker layout: supports single-file trackers or split-by-sprint trackers depending on scope.

Quick Start

Initialize the tracker and begin Sprint Refinement to convert the plan into executable code locally.

Frequently Asked Questions about implement-with-feedback

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

FAQPage Schema
How do I convert a formal plan document into local git sprints with a tracker?▼

Converting a plan document into local git sprints involves applying a disciplined workflow that translates phased designs into sprint-level implementation, updating a living tracker, and committing incrementally on a local feature branch without pushing.

Can I use a split-by-sprint tracker layout instead of a single file for sprint implementation?▼

Yes, sprint implementation supports optional tracker layouts, allowing you to choose between a single-file tracker or split-by-sprint trackers depending on the scope of your plan phases and implementation requirements.

How does local commit discipline work during sprint execution without pushing to remote?▼

Local commit discipline keeps all incremental sprint commits on disk within a local feature branch, preserving a safe development loop until you explicitly decide to push the branch or open a pull request.

What is the best way to manage plan-to-implementation work using a living tracker?▼

The best way to manage plan-to-implementation work is using a tracker-driven sprint execution approach that consolidates phased designs into refined sprints, continuously updating a living tracker alongside incremental local git commits.

Do I need a clean working tree before starting sprint refinement from a plan?▼

Yes, you need a clean working tree before starting sprint refinement because the preflight-driven setup verifies the working tree status and creates a feature-style branch before running baseline checks to ensure safe local execution.