writing-workflow

name	writing-workflow
description	How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.
compatibility	Any agent host with the OpenKnowledge MCP server configured. Installed project-local by `ok seed --pack writing-pipeline`.
metadata	{"pack":"writing-pipeline","author":"Inkeep","repository":"https://github.com/inkeep/open-knowledge-skills"}

Writing Pipeline pack — how to work here

A lean three-stage flow for short-to-medium-form writing (essays, newsletters, blog posts).

This skill is pack guidance. The platform /open-knowledge skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers the drafting flow on top.

ideas/      one-line premises, captured before they fade
   ↓ commit to writing it
drafts/     active prose; CRDT history covers revisions (no named-revision folders)
   ↓ ship
published/  shipped work; treat as immutable

Per-folder rules + agent behaviors

• ideas/ — premises, headlines, fragments. Kept short on purpose; not a draft folder. Promote into when you commit to the piece.