knowie-consolidate

Consolidates mature draft notes into long-term project knowledge files.

9|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/timcsy/semorphe --skill knowie-consolidate-timcsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowie-consolidate
Source: https://github.com/timcsy/semorphe/tree/main/.claude/skills/knowie-consolidate
Command: npx skills add https://github.com/timcsy/semorphe --skill knowie-consolidate-timcsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Undecided ideas pile up in a draft folder and either rot or get dumped wholesale into long-term notes, losing the reasoning behind them. This Skill provides a human-confirmed workflow for moving a ripe draft into a project's long-term knowledge base without losing context. ## Core Features & Use Cases - Ripeness judgment: Scans the draft/ folder and classifies each entry as a settled design, verified insight, or answered problem to decide its proper destination. - Dispatch-based consolidation: Splits one draft across multiple destinations — concepts/, experience, history/, episodes/, and the roadmap — instead of relocating the whole block. - Human confirmation gate: Proposes the dispatch plan first and writes into the long-term tier only after human approval, keeping captured notes separate from committed knowledge. - Use Case: After several sessions of brainstorming a caching design stored in draft/, run this Skill to route the design to the roadmap, the rejected alternatives to history/, and the brainstorming scene to episodes/. ## Quick Start Ask the assistant to consolidate the ripe drafts in the draft folder into the long-term knowledge tier and show the dispatch plan first.

Frequently Asked Questions about knowie-consolidate

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

FAQPage Schema
How do I consolidate draft notes into long-term project knowledge?

Run the consolidate workflow on a specific draft or let it scan the draft/ folder for ripe entries. It proposes a dispatch plan routing each piece to concepts/, experience, history/, or episodes/, then writes only after human confirmation.

What is the difference between capturing and consolidating notes?

Capturing is the intake step that stores undecided thinking in the draft/ folder. Consolidating is the exit step that moves a mature, human-confirmed draft into the long-term tier, splitting it across the appropriate knowledge files.

Can the AI write to long-term knowledge files without approval?

No. The workflow enforces a captured-not-committed invariant: the AI proposes the dispatch plan and performs reversible file moves, but writing into the long-term tier or root principles requires explicit human confirmation.

What happens to a draft after it is consolidated?

Once every piece is dispatched, the draft is retired and any decision transition is recorded in history/ with the old version marked superseded. A design promoted to the roadmap keeps its draft as in-flight rationale until the item is done.

When should a draft not be consolidated?

A draft that is not yet ripe — an unsettled design, unverified insight, or unanswered problem — stays in the draft/ folder to incubate or decay. Consolidation only applies to entries the human confirms are settled.