workflow-patterns

Structures for authoring agents and commands, plus the patterns that keep them honest. Those files are markdown with YAML frontmatter, and the templates below are given in that form.

Before adding a template, identify its consumer and verify that the runtime supports its fields. These templates follow their consumers rather than leading them. When the corpus changes shape, this file changes with it: a template prescribing a structure no consumer uses is worse than none, because it invites someone to reintroduce it.

Evidence-informed prompt changes

Start with an observed failure or a requested behavior, not a longer rule set. Check relevant project memories against current source; a past verdict is not an oracle. Keep universal contracts resident, task procedures in triggered skills, and runtime-specific capabilities in adapters.

Before using cclens counts to remove a skill, establish the analysis window, analyzer version, source freshness, runtime coverage, and parent/subagent coverage. Distinguish a Skill tool invocation from a body loaded by a file read. A missing record means unobserved use, not proven non-use. The session-format specification describes what the analyzer can observe; verify the installed implementation before relying on newer fields.