implement-with-feedback
Implement with Feedback
A disciplined, git-centric implementation workflow. Remote git logs are the primary way others monitor your work.
Workflow
Phase 1: Pre-flight Checks
-
Verify clean checkout. Run
git status. If there are ANY uncommitted changes (staged, unstaged, or untracked non-ignored files), STOP and tell the user:"Working tree is not clean. Please commit or stash your changes before starting." Do NOT proceed until the checkout is clean.
-
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. Run
git pullto ensure we're up to date.
Phase 2: Branch Creation
- Determine branch type from arguments or context. Valid prefixes:
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-remote-feedback
Execute a plan document into code through a disciplined, git-centric workflow — clean checkout, properly named branch, continuous WIP tracking, small meaningful commits, and a push after every commit so the remote branch is the monitoring channel. Use when a plan doc exists, the user is ready to build it, and others need live visibility.
8cmux
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