long-task-work

Orchestrate software feature implementation through a complete TDD pipeline.

178|43|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-task-work
Source: https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-work
Command: npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of complex software projects by breaking them down into individual features, ensuring each feature goes through a rigorous development and quality assurance process across multiple AI sessions.

Core Features & Use Cases

  • Feature-by-Feature Development: Implements one feature per cycle, maintaining focus and clean code.
  • Full TDD Pipeline: Enforces Test-Driven Development (TDD), quality gates (coverage, mutation), and acceptance testing.
  • Use Case: Building a new e-commerce platform where each new feature, like user authentication or product catalog management, is developed and tested systematically before moving to the next.

Quick Start

Use the long-task-work skill to start implementing the next feature in the project.

Frequently Asked Questions about long-task-work

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

FAQPage Schema
How do I automate test-driven development for feature implementation across multiple AI sessions?

Automating test-driven development across multiple AI sessions requires orchestrating a pipeline that manages feature dependencies and enforces quality gates. This Skill coordinates the full TDD pipeline, ensuring adherence to specifications and design documents throughout each feature cycle.

What is the best way to enforce quality gates and acceptance testing in an agile workflow?

Enforcing quality gates and acceptance testing in an agile workflow is done by implementing one feature per TDD cycle. This ensures each feature passes coverage and mutation testing before moving forward, maintaining clean code and systematic progression.

Do I need a feature-list.json file to start TDD workflow automation?

Yes, a feature-list.json file is required to start TDD workflow automation. This file defines the project's features and their requirements, serving as the necessary input to orchestrate the implementation pipeline and manage dependencies across sessions.

Can I manage feature dependencies systematically when building complex software projects?

Managing feature dependencies systematically when building complex software projects is handled by breaking the project into individual features. The Skill orchestrates each feature through a complete TDD pipeline, tracking dependencies and ensuring specifications are met before proceeding.

How does feature-by-feature development maintain focus and clean code?

Feature-by-feature development maintains focus and clean code by isolating implementation into individual TDD cycles. Each cycle includes planning, coding, quality gates, and acceptance testing, preventing scope creep and ensuring systematic validation before advancing.