From 3e46a6fa95e0518f837c2f5e3ee601d84ddc666a Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Mon, 18 May 2026 22:33:40 -0400 Subject: feat(rules): working-files convention for in-progress task artifacts I added claude-rules/working-files.md as the canonical convention. In-progress task artifacts live in working// under the project root. On task completion the files get renamed individually with a YYYY-MM-DD-- shape and moved flat into assets/ (or the area-specific assets/). Never rename the directory as a substitute for filing, since that loses the flat-searchable property of assets/. claude-templates/.ai/protocols.org gained a short reference to the rule so it propagates to every project's .ai/protocols.org on the next startup rsync. --- claude-templates/.ai/protocols.org | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'claude-templates') diff --git a/claude-templates/.ai/protocols.org b/claude-templates/.ai/protocols.org index 30b0274..57ebf87 100644 --- a/claude-templates/.ai/protocols.org +++ b/claude-templates/.ai/protocols.org @@ -158,6 +158,18 @@ Each project's =.ai/= is the scope boundary: =protocols.org=, =session-context.o Canonical rule: =~/code/rulesets/claude-rules/cross-project.md=. +** Working-Files Convention — =working//= for In-Progress Artifacts + +Every in-progress task that produces files (drafts, source documents, diagrams, scripts, sub-deliverables) gets a dedicated subdirectory under =/working/=, named after the task. All artifacts for that task live in that subdirectory until the task is marked done. + +When the task ships, files are **renamed individually** (standard form: =YYYY-MM-DD--.=) and **moved flat** into the appropriate permanent home (typically =assets/= or an area-specific =/assets/=). The working subdirectory is then empty and gets deleted. + +***Never rename the directory itself as a substitute for filing.*** The point is to keep =assets/= flat-searchable — a nested =assets/old-tech-deck-2026/slide.png= is harder to find than =assets/2026-05-18-tech-deck-vol2-slide-04-diagram.png=. + +When the user starts a new task that will produce file artifacts, propose the =working//= path before creating any files. Add or update the inbound link in =todo.org= to point at the working dir. When the user marks the task done, list every file, propose renames + permanent homes, move flat after confirmation, delete the empty subdir, update inbound links. + +Canonical rule: =~/code/rulesets/claude-rules/working-files.md=. + * Important Terminology ** "Let's run the [X] workflow" vs "I want to create an [X] workflow" -- cgit v1.2.3