<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/.ai/workflows/create-workflow.org, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-06-10T05:18:05+00:00</updated>
<entry>
<title>docs(create-workflow): document the supporting-document convention</title>
<updated>2026-06-10T05:18:05+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-06-10T05:18:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=891e1ab36aa01358bcd86026450f5a645c4eae11'/>
<id>urn:sha1:891e1ab36aa01358bcd86026450f5a645c4eae11</id>
<content type='text'>
A workflow that outgrows its inline content stores the overflow in a sibling &lt;workflow&gt;.&lt;suffix&gt;.org, linked inline. This reuses the engine.plugin dot-glob, so the drift-check and discovery glob already treat the file as owned rather than an orphan. It also travels with the workflow on promotion. I extended the INDEX drift-check note to name supporting docs alongside source plugins.
</content>
</entry>
<entry>
<title>chore(ai): initialize project notes and Claude tooling surfaces</title>
<updated>2026-05-07T02:59:52+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-07T02:59:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=d81b23ad6b6e437dfe3c338a00a4be39bc555146'/>
<id>urn:sha1:d81b23ad6b6e437dfe3c338a00a4be39bc555146</id>
<content type='text'>
Replace the seed notes.org with project-specific context (layout, install modes, task tracker location, recent inflection point). Bring in the synced template surfaces (protocols, workflows, scripts, references, retrospectives, someday-maybe) as tracked content for this content/documentation project.
</content>
</entry>
</feed>
