implement-with-remote-feedback
Implement with Remote Feedback
Execute a plan document into code, publishing every commit so the remote branch serves as the primary monitoring channel. The plan is your source of truth for WHAT to build and HOW to phase it. You are an implementer, not a designer.
Preflight
Locate the plan. The skill starts from a completed plan. If $ARGUMENTS points to an existing plan doc, use it. Otherwise glob docs/plans/plan_*.md and ask the user to pick one. If no plan exists, STOP and tell the user this skill requires a plan doc as input — do NOT invent scope or design from scratch.
Read the plan in full. Use the Read tool WITHOUT limit/offset. The plan IS your source of truth for scope, phases, and Success Criteria. Do not redefine them. If they need to change, say so and OFFER to switch back to /plan — never switch unilaterally.
Verify the working tree is clean. Run git status. If there are ANY uncommitted or untracked non-ignored changes, STOP and tell the user:
"Working tree is not clean. Please commit or stash your changes before starting."
Verify we are on main/master. If not, warn the user and ask whether to continue from the current branch or switch to main first.
Pull latest. git pull to ensure we're up to date.
Confirm the branch name with the user. The default is <type>/<slug>, where <slug> matches the plan's slug. Valid types:
feature/— new functionality
More from xalior/agent-skills
agent-feedback
Analyze other agents' sessions and construct targeted corrective prompts to fix mistakes, correct context drift, or drive home task requirements
10implement-with-feedback
Git-centric implementation workflow. Enforces clean checkout, creates a properly named branch, tracks progress in a WIP markdown file, and commits continuously so git logs serve as the primary monitoring channel. Use when starting instructed, offer for any plan-based implementation task.
7cmux
Control the cmux terminal multiplexer. Use this skill when the user asks to manage terminal panes, workspaces, windows, browser splits, or interact with cmux in any way. Also use when you need to read other terminal screens, send commands to other panes, create splits, or manage the terminal layout.
2pre-plan
Interactive requirement refinement before planning starts. Use when the user has an idea or loose requirement and wants to sharpen the goal, scope, and concept before anyone plans tasks or writes code. Produces a single markdown document that survives context reset.
1plan
Interactively turn a refined pre-plan (goal, scope, concept) into a concrete implementation plan — phases, changes, and success criteria. The user stays in the driver's seat for design decisions. Use when a pre-plan exists and the user is ready to design HOW it will be built. Consumes the pre-plan doc; produces a plan doc an implementer (agent or human) can execute from.
1nicelicense
Add or identify open-source licenses in projects using the nicelicense CLI. Use this skill when the user asks to add a license, change a license, check what license a project uses, or manage LICENSE files.
1