aif-implement

Coordinate TaskList, TaskGet, and TaskUpdate to execute plan-driven implementation tasks.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/afterwork/arra-aif --skill aif-implement-afterwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-implement
Source: https://github.com/afterwork/arra-aif/tree/main/.cursor/skills/aif-implement
Command: npx skills add https://github.com/afterwork/arra-aif --skill aif-implement-afterwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates and coordinates the execution of plan-driven implementation tasks, preserving progress across sessions and ensuring plan checkboxes reflect real status.

Core Features & Use Cases

  • Sequential task execution: starts from the next pending task, marks it in_progress, and completes it before moving on.
  • Progress persistence: saves state between sessions and can resume where left off.
  • Plan synchronization: updates the corresponding - [ ] / - [x] checkbox in the plan file immediately upon completion, and can override plan sources from branch or fixed plan files.
  • Context-aware updates: reads task details, modifies code, and updates related documentation or architecture notes when needed.

Quick Start

Run /aif-implement to resume from the next incomplete task or specify a plan with @path to execute a defined plan.

Frequently Asked Questions about aif-implement

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

FAQPage Schema
How do I resume software development task execution across multiple sessions?

Plan synchronization updates the corresponding checkbox in the plan file immediately upon task completion. It marks items in real time and supports overriding plan sources directly from branch or fixed plan files.

What is the best way to track sequential task progress for AI-assisted workflows?

Yes, you can execute a defined plan by specifying a plan with @path. This allows the system to read task details, modify code, and update related documentation or architecture notes when needed.

Do I need a specific plan file format to manage versioned plans?

Explicit plan overrides are supported by allowing you to switch plan sources from a specific branch or fixed plan files. This ensures the execution follows the correct versioned plan during commit checkpoints.

Why does my plan checkbox not update after task completion?

Plan checkboxes fail to update when the system cannot synchronize the plan file during task execution. Ensure the plan file is accessible and uses the standard - [ ] / - [x] syntax for real-time updates to apply correctly.