One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill session-harvest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-harvest
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/session-harvest
Command: npx skills add https://github.com/hirokimry/vibecorp --skill session-harvest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures knowledge created during a working session so important decisions, patterns, and implementation notes do not disappear after the conversation ends.

Core Features & Use Cases

  • Session knowledge extraction: Pulls useful insights from the current session’s conversation and recent changes.
  • Role-based delegation: Routes findings to CTO, CPO, CISO, CFO, and CLO so they can update the right knowledge, rules, or docs.
  • Buffer branch workflow: Writes updates into a dedicated knowledge/buffer worktree before they are later merged into main.
  • Use case: After a debugging or design session, use this Skill to preserve the conclusions, constraints, and reusable lessons for future development runs.

Quick Start

Ask the AI to harvest the current session’s insights into the buffer branch for this repository.

Frequently Asked Questions about session-harvest

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

FAQPage Schema
How do I save session insights and implementation notes for future development runs?

To save session insights, extract decisions, patterns, and implementation notes from the current conversation and write them into a dedicated knowledge buffer branch. This preserves reusable knowledge across iterations before merging into the main branch.

What is the best way to retain development decisions and constraints after a debugging session ends?

The best way to retain development decisions is to harvest session insights into a buffer worktree. This safely isolates knowledge updates and documentation changes before they are merged into the main repository.

How does role-based delegation work for updating documentation and rules?

Role-based delegation routes extracted session findings to executive roles like CTO, CPO, CISO, CFO, and CLO. Each role is responsible for updating the specific knowledge, rules, or documentation relevant to its domain.

Can I write documentation updates directly to the main branch during a working session?

No, documentation updates are written into a dedicated knowledge/buffer worktree for safe write isolation. This buffer branch workflow ensures changes are retained and reviewed before later merging into main.

Does session harvesting require complex dependencies to manage branch-aware knowledge?

No dependencies are required. Session harvesting applies branch-aware delegation, limited context handling, and safe write isolation natively to update knowledge and documentation across iterations.