long-task-increment

Integrate new requirements into SRS, design, and UCD documents with Git version control.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill manages the complex process of adding, modifying, or deprecating requirements in a live software project, ensuring all documentation and code structures are updated systematically.

Core Features & Use Cases

  • Incremental Requirements Elicitation: Collects new or changed requirements using structured methods (EARS template).
  • Impact Analysis: Assesses how changes affect existing features and design.
  • In-place Document Updates: Modifies SRS, Design, and UCD documents directly, preserving history via Git.
  • Feature List Management: Updates feature-list.json to reflect new, modified, or deprecated features.
  • Use Case: A product manager needs to add a new user authentication method to an existing application. This Skill will guide them through defining the new requirements, analyzing the impact on the current architecture, updating the design documents, and decomposing the new authentication flow into manageable features.

Quick Start

Use the long-task-increment skill to add new requirements to the project.

Frequently Asked Questions about long-task-increment

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

FAQPage Schema
How do I integrate new requirements into existing software documentation?

To integrate new requirements into existing software documentation, this Skill elicits changes using the EARS template, performs impact analysis, and applies in-place updates to SRS, design, and UCD documents while preserving version history via Git.

What is the best way to manage incremental software development and update feature lists?

Managing incremental software development is handled by this Skill through feature decomposition, where it modifies the `feature-list.json` to accurately reflect new, modified, or deprecated features for iterative development cycles.

How does impact analysis work when modifying existing project requirements?

Impact analysis for modified requirements works by assessing how the requested changes affect existing features and design structures, ensuring project integrity through rigorous validation before applying in-place document updates.

Do I need a specific input format to add new requirements to an agile project?

Yes, you need to provide structured input via `increment-request.json` to define the new or modified requirements, which ensures the changes are systematically analyzed and integrated into the existing project documentation.

Can I use Git version control to preserve project history during requirement updates?

Git version control is used natively by this Skill to preserve project history, ensuring that all in-place updates to SRS, design, and UCD documents are tracked and maintained systematically during requirement integration.