org

Run and bucket project work in focused spike docs with a conceptual doc, a to-do doc, TODO.md as an index, scratch promotion, human QA tracking, durable handoff notes, active-spikes placement, archival, and continuation links between related phases of work. Use when starting, continuing, promoting, superseding, archiving, or reviewing project work that should leave navigable history.

Triage a project's loose scratch inbox at docs/scratch/misc.md into addressed items, future ideas, pinned issues, thematic scratch docs, numbered misc buckets, active spikes, or durable docs. Use when the user asks to review misc notes, route loose observations, clean up scratch material, cluster possible future work, or process a docs/scratch/misc.md inbox.

Capture conceptual someday Open Austin org/tooling/process ideas in docs/scratch/future-ideas.md without promoting them to active spikes. Use when the user has a far-future automation idea, process direction, GitHub/org tooling capability, documentation concept, or exploratory idea that is more coherent than misc intake but not ready for scoped work.

Preserve an unresolved Open Austin org/tooling/process issue in docs/pinned-issues.md without turning it into a GitHub issue backlog item, active spike, or durable decision. Use when the user says to put a pin in something, circle back later, defer a thorny org/process/tooling question, revisit pinned issues, or route a pin into active work, future ideas, misc intake, or a decision record.

Update existing repo-local skill copies from global seed skills while preserving local divergence. Use when the user asks to refresh, sync, compare, or update local skills from their global/source versions, especially after global skill taxonomy or workflow changes.

Produce the weekly Open Austin org summary, broken out per team into separate Slack channels, from a fresh snapshot. Use when the user asks for a 'weekly summary', 'weekly update', 'org digest', or 'what's going on this week'.