Translate approved issue specifications into code with a plan-first workflow.
npx skills add https://github.com/arttttt/CMIDCABot --skill implement-arttttt
Please help me install this Agent Skill. Skill: implement Source: https://github.com/arttttt/CMIDCABot/tree/main/.codex/skills/implement Command: npx skills add https://github.com/arttttt/CMIDCABot --skill implement-arttttt
This skill translates issue specifications into concrete code implementations only after explicit approval, reducing misinterpretation and unreviewed changes.
Initiate a task by invoking the implement skill with the issue identifier. The skill will read the issue, propose an implementation plan, and await your approval before proceeding.
High-intent search queries and answers about installing and using this skill.
A plan-first implementation approach requires analyzing issue specifications, drafting an implementation plan, and securing explicit approval before writing any code. This workflow enforces structured development steps including branch creation and conventional commits to prevent unreviewed changes.
A plan-first workflow requires analyzing issue specifications, drafting an implementation plan, and securing explicit approval before writing any code. This workflow enforces structured development steps including branch creation and conventional commits to prevent unreviewed changes.
Standardized branch naming and commit discipline are enforced by applying an interaction contract that governs feature branch creation and requires conventional commit messages. This ensures structured development steps are followed after stakeholder approval of the implementation plan.
Implementation cannot proceed without explicit stakeholder approval. The skill enforces an interaction contract where code changes are blocked until the drafted implementation plan receives confirmation, ensuring no unreviewed changes are made from the issue specifications.
The limitation of approval-driven execution is that implementation is strictly blocked until stakeholder sign-off is received. This plan-first approach requires explicit confirmation for each issue specification, which may slow down rapid prototyping or independent development scenarios.
VoDaiLoczConvert project plans and specifications into structured issue trackers.
manastalukdarSquash Git commits, run tests, and clean up branches.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.
Adrian-opoExecute complex plans in controlled batches with review checkpoints.
