Execute implementation plans by writing code, running tests, and committing changes.
npx skills add https://github.com/DFilipeS/praxis --skill px-implement
Please help me install this Agent Skill. Skill: px-implement Source: https://github.com/DFilipeS/praxis/tree/main/praxis/skills/px-implement Command: npx skills add https://github.com/DFilipeS/praxis --skill px-implement
Bridges the gap between a written implementation plan and production code by enforcing a disciplined, incremental process that prevents guesswork, preserves reviewability, and ensures acceptance criteria are verified.
Run px-implement and provide the path to a ready plan file, for example .ai-workflow/plans/20260222-offline-first-sync-phase-1.md, then follow prompts to select a branch and implement each step.
High-intent search queries and answers about installing and using this skill.
To turn an implementation plan into working code, you execute the plan file by following its ordered steps, prompting for branch strategy, running tests, and making incremental commits to verify acceptance criteria.
To enforce incremental git commits during feature implementation, the workflow prompts you for a branching strategy and makes reviewable commits after completing each planned step and running validation checks.
The best way to ensure acceptance criteria are met is to run appropriate tests or checks after each implementation step, verifying that the production code satisfies the requirements before handing off to reviewers.
Yes, you can use an AI agent to automate software development workflows by loading plan files marked ready, updating their status to in-progress, and executing the defined implementation steps sequentially.
You need a markdown plan file marked ready, such as a file located in the .ai-workflow/plans/ directory, containing ordered implementation steps, acceptance criteria, and branch strategies to begin plan-driven implementation.
You should run automated reviewers in a fresh thread after implementing code to ensure a clean validation environment, preserving reviewability and verifying that the incremental commits meet the acceptance criteria without prior context interference.
jaisonerickBreak plan documents into ordered markdown story files with agent assignments.
oletiziAutomate feature shipping from worktree validation to pull request creation.
zeronx798Scan staged git changes for security issues and quality regressions.
auerbachbVerify acceptance-criteria checkboxes in GitHub pull requests against repository code.
