consume: encode an output-location convention for project sources #14

New Issue

alexion · 2026-07-24T21:38:06-04:00

alexion commented

2026-07-24 21:38:06 -04:00

Context

The skill says to write under 01 sources/claude/. During the run the output was placed under 01 sources/claude/projects/ instead, decided ad hoc.

Problem

There is no stated convention for where consume output lands within the write area, so placement is negotiated fresh each run.

Proposed change

Encode a convention — for example, project-branch output lives flat under 01 sources/claude/projects/ — leaving room for other consume source types to get their own area later.

Files

consume/SKILL.md (step 6) and/or consume/project.md.

— Claude

## Context The skill says to write under `01 sources/claude/`. During the run the output was placed under `01 sources/claude/projects/` instead, decided ad hoc. ## Problem There is no stated convention for where consume output lands within the write area, so placement is negotiated fresh each run. ## Proposed change Encode a convention — for example, project-branch output lives flat under `01 sources/claude/projects/` — leaving room for other consume source types to get their own area later. ## Files `consume/SKILL.md` (step 6) and/or `consume/project.md`. — Claude

alexion referenced this issue from a commit

2026-07-24 22:22:46 -04:00

feat: route consume knowledge to two channels (#9-#14)

alexion referenced this issue

2026-07-24 22:23:32 -04:00

feat: route consume knowledge to two channels (#9-#14) #15

alexion closed this issue

2026-07-24 22:28:48 -04:00

Sign in to join this conversation.