implement-task

Execute the full Binder Task lifecycle from selection through verification.

39|5|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/mpazik/Binder --skill implement-task-mpazik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-task
Source: https://github.com/mpazik/Binder/tree/main/examples/workflow/skills/implement-task
Command: npx skills add https://github.com/mpazik/Binder --skill implement-task-mpazik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you take an existing Binder Task from the backlog and move it through investigation, design, implementation, verification, and completion without losing the thread.

Core Features & Use Cases

  • Guided task handling: Picks the right next guide based on task fields like status, specification, linked problems, and whether tests are still needed.
  • Root-cause discovery and documentation: When a fix needs diagnosis, it guides you to reproduce, trace, and record the real cause and trigger steps in the task.
  • Contract-first engineering: For design-worthy tasks, it produces a structured specification including approach, contracts, file plan, and validation steps.
  • Collaboration on open questions: For tasks linked to Problem records, it drives an IBIS-style resolution and records decisions in task details or separate records.

Quick Start

Pick up a task by providing its key, or omit the key to choose from the active lists of pending/active tasks.

Frequently Asked Questions about implement-task

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

FAQPage Schema
How do I manage the full task lifecycle from backlog to completion without losing context?

To manage the full task lifecycle without losing context, you can execute a Binder Task from selection through investigation, design, implementation, and verification, ensuring the thread is maintained until the task is marked complete.

How do I perform root cause analysis and document it for a bugfix task?

Root cause analysis for a bugfix task involves reproducing the issue, tracing the real cause, and recording the trigger steps directly in the task metadata. This guides the fix and ensures the diagnosis is documented before implementation.

What is the best way to implement a contract-first specification for a new feature?

Contract-first specification for a new feature is implemented by producing a structured specification that includes the approach, contracts, file plan, and validation steps before writing code, ensuring design-worthy tasks are fully scoped.

Can I resolve open questions linked to Problem records during task implementation?

Yes, you can resolve open questions linked to Problem records during task implementation by driving an IBIS-style resolution. Decisions are then recorded in the task details or separate linked records for future reference.

Does task management routing depend on the current status and specification fields?

Yes, task management routing depends on the current status and specification fields. The system reads task records via Binder CLI and routes to the appropriate guide based on these fields to determine the next required action.

How do I ensure verification before marking a task as complete?

To ensure verification before marking a task as complete, the task lifecycle process checks whether tests are still needed and validates the implementation against the specification before updating the task status to completion.