writing-pipeline

Name: writing-pipeline
Author: inkeep

3.1kstars191forks

How to install writing-pipeline?

inkeep/open-knowledge/writing-pipeline

$npx -y skills add inkeep/open-knowledge --skill writing-pipeline

Installs into the current project.

Summary

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. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or

Files · 1

View on GitHub

SKILL.md

1	# Writing Pipeline pack — how to work here
2
3	A lean three-stage flow for short-to-medium-form writing (essays, newsletters, blog posts):
4
5	```
6	ideas/ one-line premises, captured before they fade
7	↓ commit to writing it
8	drafts/ active prose; CRDT history covers revisions (no named-revision folders)
9	↓ ship
10	published/ shipped work; treat as immutable
11	```
12
13	## Per-folder rules + agent behaviors
14
15	- `ideas/` — premises, headlines, fragments. Kept short on purpose; not a draft folder. Promote into `drafts/` when you commit to the piece. Agent: review ideas idle more than 30 days and surface them to park or promote.
16	- `drafts/` — active prose. Frontmatter tracks `status: drafting/review`, word count, parent idea. Agent: review drafts idle more than 14 days; for drafts in review, suggest publication targets based on `target_form`. If a piece needs research notes, create `drafts/<slug>/research/` on demand rather than a top-level folder.
17	- `published/` — shipped work; carries `published_at`, `canonical_url`, `channel`. Treat as immutable; to revise, copy to a new draft. Agent: on publish, auto-fill `canonical_url` when a Substack / Ghost / Mirror URL is pasted into the file.
18
19	## Templates
20
21	Create with `write({ document: { path, template: "<name>" } })`. Templates carry only structure; section meaning lives here, not in the document body.

People who liked this also viewed

6 picks

Type

writing-pipeline

3.1kstars191forks

View on GitHub

How to install writing-pipeline?

inkeep/open-knowledge/writing-pipeline

$npx -y skills add inkeep/open-knowledge --skill writing-pipeline

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Writing Pipeline pack — how to work here
2
3	A lean three-stage flow for short-to-medium-form writing (essays, newsletters, blog posts):
4
5	```
6	ideas/ one-line premises, captured before they fade
7	↓ commit to writing it
8	drafts/ active prose; CRDT history covers revisions (no named-revision folders)
9	↓ ship
10	published/ shipped work; treat as immutable
11	```
12
13	## Per-folder rules + agent behaviors
14
15	- `ideas/` — premises, headlines, fragments. Kept short on purpose; not a draft folder. Promote into `drafts/` when you commit to the piece. Agent: review ideas idle more than 30 days and surface them to park or promote.
16	- `drafts/` — active prose. Frontmatter tracks `status: drafting/review`, word count, parent idea. Agent: review drafts idle more than 14 days; for drafts in review, suggest publication targets based on `target_form`. If a piece needs research notes, create `drafts/<slug>/research/` on demand rather than a top-level folder.
17	- `published/` — shipped work; carries `published_at`, `canonical_url`, `channel`. Treat as immutable; to revise, copy to a new draft. Agent: on publish, auto-fill `canonical_url` when a Substack / Ghost / Mirror URL is pasted into the file.
18
19	## Templates
20
21	Create with `write({ document: { path, template: "<name>" } })`. Templates carry only structure; section meaning lives here, not in the document body.

People who liked this also viewed

6 picks

Type