implement-tasks

Executes approved task plans through worktree isolation, TDD loops, and PR creation.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill implement-tasks-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-tasks
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/implement-tasks
Command: npx skills add https://github.com/islamu-ngo/Event --skill implement-tasks-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing an approved implementation plan involves many error-prone steps: setting up isolated worktrees, resuming in-flight work, running the right tests at the right time, triaging failures, and creating compliant pull requests. This Skill orchestrates that entire lifecycle so approved plans are executed consistently without losing context or polluting the main workspace. ## Core Features & Use Cases - Topology Discovery & Resume: Automatically detects whether a task runs in a fresh worktree, an in-flight worktree, or in-tree on develop, and resumes from the first unchecked task. - Red/Green/Refactor Phase Loops: Enforces test-first development with tiered verification rings (fast sliced tests, phase gates, full multi-database matrix) and three-tier failure triage that quarantines pre-existing baseline rot. - PR Lifecycle Management: Handles semantic phase commits, pre-PR rebases, Release Impact checklist generation, worktree parking for CI follow-up, and teardown on user confirmation. - Use Case: After approving a plan in dev/active/<task>/, tell the agent to execute it; the Skill creates an isolated worktree, implements each phase with tests, commits semantically, and opens a compliant PR to develop. ## Quick Start Execute the approved task plan in dev/active/my-feature using the implement-tasks workflow and open a pull request when finished.

Frequently Asked Questions about implement-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an in-flight implementation task in a git worktree?▼

Run the resume command for the task; the Skill detects the existing .worktrees/<task> directory via git worktree list, sets the execution context there, reads the context and tasks files, verifies the test baseline, and continues from the first unchecked task.

How does the Skill handle test failures during implementation?▼

It applies three-tier triage: direct feature regressions are fixed in-phase, integration ripples are aligned or escalated via a Decision Brief, and pre-existing baseline rot is verified against clean origin/develop and quarantined in the context file without derailing the task.

Can I run an approved plan directly on the develop branch without a worktree?▼

Yes. If dev/active/<task> exists at the repository root and work is in progress or the user mandates in-tree execution, the Skill respects that topology and executes in the root workspace without creating or moving anything into a worktree.

Why does the Skill park the worktree after creating a pull request?▼

The worktree remains parked so CI failures and bot review comments (Copilot, CodeQL) can be resolved immediately in place with zero setup overhead. It is only removed after the user explicitly confirms the PR is approved or merged.

What happens when a large migration spans many cohorts?▼

The Skill uses a hub-and-spoke topology: a lead hub worktree accumulates verified commits from ephemeral spoke worktrees named <task>--<cohort>, bounds active worktrees to 3-5, prunes spokes after integration, and issues a single PR from the hub.