harvest

Decompose reviewed implementation plans into feature-task-subtask backlog hierarchies.

1|Updated Oct 17, 2025

Search Tags:#dependencies #task breakdown #backlog #dry run #implementation units #plan decomposition

Ready to run

npx skills add https://github.com/softwaresalt/csv-managed --skill harvest-softwaresalt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harvest
Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/harvest
Command: npx skills add https://github.com/softwaresalt/csv-managed --skill harvest-softwaresalt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The harvest skill converts an already reviewed implementation plan into a structured backlog of features, tasks, and subtasks so teams can execute without re-interpreting the plan.

Core Features & Use Cases

Reviewed-plan decomposition: Transforms approved plan content into a backlog-ready hierarchy with clear parent-child structure and explicit verification exit states.
Dependency wiring and validation: Extracts dependency edges from the plan and wires them when supported by the backlog tooling, while validating plan readiness before any mutations.
Dry-run reporting for safe preview: Generates a proposed structure and reports counts without creating entries when dry_run is enabled.

Quick Start

Use the harvest skill with plan=docs/plans/2026-01-15-add-csv-schema-snapshot-plan.md and dry_run=true to preview the feature/task/subtask structure before writing anything to the backlog.

Frequently Asked Questions about harvest

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

FAQPage Schema

How do I decompose an implementation plan into a structured backlog?▼

Decomposing an implementation plan into a structured backlog involves breaking down reviewed plan content into a feature-task-subtask hierarchy with explicit parent-child ordering, dependency wiring, and verification-slice subtasks for execution readiness.

What is plan decomposition for task breakdown?▼

Plan decomposition for task breakdown is the process of transforming approved implementation units into a backlog-ready hierarchy, ensuring teams can execute deterministically without re-interpreting the original plan content.

Can I preview a backlog structure before writing entries to the task tracker?▼

Yes, you can preview a backlog structure by running in dry-run mode, which generates a proposed feature-task-subtask hierarchy and reports counts without creating any entries or performing mutations in the backlog tooling.

How are dependencies wired during backlog generation from a plan?▼

Dependencies are wired during backlog generation by extracting dependency edges from the reviewed plan and wiring them into the backlog tooling, while validating plan readiness before any structural mutations occur.

Does backlog generation enforce ordering for implementation units?▼

Yes, backlog generation enforces parent-first ordering for task items, ensuring that the feature-task-subtask hierarchy maintains a deterministic execution sequence aligned with the reviewed implementation plan.

When should I not use automated plan decomposition for task breakdown?▼

You should avoid automated plan decomposition if the implementation plan has not been fully reviewed and validated, as the process requires reading the plan fully and enforcing readiness checks before executing any backlog mutations.