_collection

Verify per-step task note files and generate a consolidated task README.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/HahyeonJeon/gobbi --skill collection-hahyeonjeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: _collection
Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_collection
Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill collection-hahyeonjeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill verifies that all per-step subdirectories contain their expected note files and writes the task-level README to summarize progress and outcomes.

Core Features & Use Cases

  • Note verification: ensure required files exist across ideation/, plan/, research/, and execution/.
  • README generation: produce a task-level README and update the parent index with this task.
  • Gotcha recording: capture and surface corrections or surprises via the gotcha mechanism.

Quick Start

Run gobbi note collect to verify notes and generate the task README.

Frequently Asked Questions about _collection

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

FAQPage Schema
How do I verify task note completeness across project subdirectories?▼

To verify task note completeness, this Skill scans per-step subdirectories like ideation/, plan/, research/, and execution/ to ensure required files exist. It then generates a gap report to identify any missing documentation artifacts.

What is the best way to generate a task-level README from subdirectory notes?▼

Generating a task-level README is handled by validating and consolidating notes from per-step subdirectories. It summarizes progress and outcomes into a single README file while updating the parent index with the current task status.

Does note verification work without evaluation artifacts in the subdirectories?▼

Note verification does work without evaluation artifacts, as these artifacts are optional. The process requires per-step subdirectories to exist and will report gaps only when expected required note files are missing.

How do I record and surface gotchas or unexpected issues during task execution?▼

To record gotchas during task execution, this Skill provides a mechanism to capture corrections or surprises. It surfaces these recorded gotchas in the final validated README to ensure task context is preserved.

When should I run note collection to verify my task documentation?▼

You should run note collection after completing Ideation, Plan, Research, and Execution phases. This ensures all per-step subdirectories are populated and allows the Skill to validate required files before generating the consolidated README.