Execute PLAN.md tasks in order with atomic commits and TDD.
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-execute
Please help me install this Agent Skill. Skill: gsd-execute Source: https://github.com/alo-exp/silver-bullet/tree/main/.forge/skills/gsd-execute Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-execute
Execute PLAN.md with deterministic task execution, atomic commits, and enforced testing discipline to ensure plan-to-production traceability.
Ensure PLAN.md exists, then run the GSD Execute Phase to carry out tasks in order with tests and commits.
High-intent search queries and answers about installing and using this skill.
To execute PLAN.md tasks in strict order with TDD discipline, you run the GSD Execute Phase. It automates stepwise task execution, writes failing tests before implementation, and verifies each task before proceeding to the next.
To handle deviations when implementing a planned software task sequence, the execution process documents the divergence and ensures safe recovery before continuing. Deviations are logged with proper conventional commit messages to maintain plan-to-production traceability.
Atomic commit discipline in test-driven development is committing each implemented task individually with conventional prefixes after tests pass. This approach ensures deterministic execution and strict plan-to-production traceability for software projects.
Yes, you need an existing PLAN.md file to automate task execution with atomic commits. The execution automation requires this file to define the work, enforce strict task order, and apply verification flags during the implementation phase.
The best way to ensure plan-to-production traceability in DevOps is combining deterministic task execution with atomic commits and enforced testing discipline. This methodology guarantees each planned step is implemented, verified, and documented sequentially.
When a verification flag fails during PLAN.md task execution, the stepwise process halts to ensure safe recovery. The deviation from the planned step is documented with a proper commit message before continuing with the next task.
t-hasuikeGenerate a structured reference guide for project documentation during legacy-system investigations.
SilentEchoeCommit and push code changes to a Git repository with conventional commit messages.
itzcullDefine conventional commit types and TDD-style commit rhythms for software projects.
kousukefEnforce test-first development with red-green-refactor cycles before production code.
