Run the Praxis forge workflow to advance a software change through design, implementation, review, and improvement.
npx skills add https://github.com/chriswch/praxis --skill forge-chriswch
Please help me install this Agent Skill. Skill: forge Source: https://github.com/chriswch/praxis/tree/main/skills/forge Command: npx skills add https://github.com/chriswch/praxis --skill forge-chriswch
The Forge skill automates the manual orchestration work required to move a software change quickly from a primary specification checkpoint through design, implementation, review, and improvement, reducing context switches and operator overhead for rapid delivery.
/forge or when tests are not being authored and auto-advancement is preferred.Run the forge workflow to rapidly advance the current change from a single spec through design, implementation, review, and improvement within the Praxis repository.
High-intent search queries and answers about installing and using this skill.
Automating software change orchestration advances a change through design, implementation, review, and improvement stages from a single main spec checkpoint. The workflow coordinates sibling stage skills while maintaining main session orchestration to reduce operator overhead.
Multi-stage workflow automation for rapid code delivery moves a change across clarifying-intent, slicing-stories, sketching-design, rapid-implementing, code-reviewing, and code-improving stages. It uses a single checkpoint and auto-advancement to minimize context switches during fast-paced engineering.
Yes, Codex-driven automation is designed to accelerate small-to-medium scoped changes. It keeps orchestration in the main session while delegating stage work to sibling skills and reusing runtime contracts for rapid delivery when auto-advancement is preferred.
No, the Praxis Forge workflow does not require writing tests to advance stages. It is specifically built for rapid delivery scenarios where tests are not being authored and auto-advancement across stages is preferred over manual stage validation.
Coordinating sibling stage skills during code implementation is handled by the main session orchestrator. It delegates work to sibling skills for rapid-implementing, code-reviewing, and code-improving while utilizing repository-level run and stage-result contracts for validation and resume bookkeeping.
You should avoid automated workflow orchestration when manual oversight is required across stages, or when test authoring is mandatory for your delivery pipeline. The workflow relies on a single checkpoint and auto-advancement, which may bypass necessary manual validation for complex changes.
hatch3rCreate and execute validated YAML workflow recipes for hatch3r agents.
jtvarisCoordinate multi-disciplinary design roles to produce a level design document.
joshkellett87Plan and validate design ideas through guided, one-question-at-a-time dialogue with automatic documentation generation.
amanikExecute CEO, design, and engineering review skills sequentially with auto-decisions.