Verified:GitHub

aif-implement

Automates project workflows by orchestrating tasks, managing GitLab/GitHub operations, and coordinating CI/CD pipelines through customizable triggers and handlers. It económizes effort, reduces manual overhead, and ensures consistency across your entire SDLC from a single, unified interface.

Updated Aug 23, 2026

Search Tags:#automation #workflow #task-management #plan-execution #session-persistence #aif-implement

One-click install

npx skills add https://github.com/ichinya/idshka --skill aif-implement-ichinya

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: aif-implement
Source: https://github.com/ichinya/idshka/tree/main/.codex/skills/aif-implement
Command: npx skills add https://github.com/ichinya/idshka --skill aif-implement-ichinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates end-to-end implementation work from plan loading to task execution, progress tracking, and finalization, including optional handoff synchronization and artifact updates.

Core Features & Use Cases

Orchestrates plan loading from git or plan directories, resolving the active plan, and resuming from the next pending task.
Tracks tasks with statuses (pending, in_progress, completed), updates the plan checkboxes, and persists progress across sessions.
Applies project rules and skill-context overrides, and updates key artifacts like DESCRIPTION.md and ARCHITECTURE.md when structure or tech decisions change.
Supports Handoff-mode coordination with an external handoff system and optional review/done signaling.

Quick Start

Run the skill with no arguments to resume the next pending task, or specify a plan file with @<path> to start a particular plan.

Frequently Asked Questions about aif-implement

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

FAQPage Schema

How do I automate task plan execution and track progress across sessions?▼

Automate task plan execution by loading the plan, tracking task statuses, updating checkboxes, and persisting progress across sessions. It coordinates code changes and enforces progress checkpoints end-to-end.

How does session persistence work when resuming an in-progress task plan?▼

Session persistence works by tracking task states like pending, in_progress, and completed. When resuming, the workflow resolves the active plan and automatically continues from the next pending task.

Can I update project artifacts like architecture files automatically during plan execution?▼

You can update project artifacts automatically during plan execution. When code changes occur, the workflow updates key artifacts like DESCRIPTION.md and ARCHITECTURE.md to reflect structural or technical decisions.

Does this workflow support handoff synchronization with external MCP systems?▼

The workflow supports Handoff-mode coordination with external MCP/Handoff systems. It enables optional review and done signaling to synchronize task states across different execution environments.

What is the best way to load a specific task plan file for execution?▼

The best way to load a specific plan is to specify the plan file path using the @<path> argument. Running with no arguments automatically resumes the next pending task from the active plan.

When should I not use an automated plan execution workflow?▼

You should avoid automated plan execution for tasks without a structured plan file or when your project lacks the required artifact files like DESCRIPTION.md and ARCHITECTURE.md needed for automatic updates.