harvest

Orchestrates the post-implementation harvest of completed feature artifacts with sequential sub-skill dispatch and approval-based archiving.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/AbsolutSystems/absolutpowers --skill harvest-absolutsystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harvest
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/harvest
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill harvest-absolutsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual coordination work at the end of a feature cycle by handling the harvest phase in one place, so you do not have to remember which documentation, learning, and archival steps should happen next.

Core Features & Use Cases

  • Sequential orchestration: Runs the harvest pipeline in a fixed order so knowledge capture happens consistently after implementation.
  • Graceful delegation: Calls optional sub-skills only when they exist, skipping missing ones without breaking the workflow.
  • Documentation and architecture updates: Triggers feature documentation and module architecture regeneration when the change actually warrants it.
  • Controlled archiving: Moves completed planning and task artifacts into archive storage only after completion checks and user approval.
  • Use case: After a feature is finished, use this Skill to capture reusable learnings, refresh module docs, and archive the feature artifacts cleanly.

Quick Start

Give the Skill the path to the completed feature planning or tasks file and let it run the harvest sequence, update documentation when needed, and prepare any archive move for approval.

Frequently Asked Questions about harvest

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

FAQPage Schema
How do I automate documentation updates after feature implementation?

Automating documentation updates after feature implementation requires orchestrating a harvest phase. This skill runs a sequential pipeline to trigger module documentation and architecture regeneration only when structural changes warrant them, ensuring docs stay current without manual intervention.

What is the best way to archive completed feature planning and task files?

The best way to archive completed feature planning files is through a controlled archival process. This skill moves task artifacts into archive storage only after completion checks pass and the user approves the final archive summary, ensuring safe and deliberate file relocation.

How do I capture reusable patterns after finishing a software feature?

Capturing reusable patterns after finishing a software feature is handled by a post-implementation harvest phase. This skill orchestrates knowledge capture workflows that learn from the completed artifacts, systematically extracting and recording patterns for future development cycles.

Does the feature harvest pipeline break if optional sub-skills are missing?

The feature harvest pipeline does not break if optional sub-skills are missing. It uses graceful delegation to call sub-skills only when they exist, skipping missing ones without halting the deterministic sequencing of the harvest workflow.

When do I need to regenerate architecture docs during the harvest phase?

You need to regenerate architecture docs during the harvest phase when a feature implementation actually warrants structural changes. The orchestration pipeline applies per-step gates to determine if module architecture regeneration is necessary before committing any documentation updates.