log-future-idea

name	log-future-idea
description	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.

Log Future Idea

This is the Open Austin org repo's own future-idea process. It is project authority here, not fallback seed material.

Purpose

Use this skill for conceptual future material: ideas that may matter someday but are not ready to become active Open Austin org tooling work.

Default file:

docs/scratch/future-ideas.md

Create it only when the user asks to log a future idea or an existing misc/future-idea triage pass needs it.

Taxonomy

Use the first matching destination:

• docs/decisions/ for settled durable repo rules.
• docs/pinned-issues.md for unresolved issues intentionally preserved for later.
• docs/scratch/future-ideas.md for conceptual someday material.
• docs/scratch/misc.md for raw observed friction, QA nits, bugs, and issue intake.
• docs/active-spikes/ for active scoped work.

Future ideas are more conceptual and farther-horizon than misc notes. They are not more important, more approved, or more likely to happen.

What Belongs Here

Good future idea entries are coherent enough to reread later as an idea:

• future GitHub/org automation capabilities
• board/process improvement concepts that need a real phase later
• documentation or contributor-support directions that are too early to scope
• exploratory architecture or data-flow ideas
• retired ideas worth remembering as possible later context

Do not put raw QA observations, nit lists, bugs, active org issues, board triage notes, or unresolved decision questions here. Put those in misc.md, pinned-issues.md, active spikes, or GitHub issues as appropriate.

Workflow

1. Read the current user request and docs/scratch/future-ideas.md if it exists.
2. Check nearby docs/scratch/misc.md, docs/pinned-issues.md, and active spikes if the idea might already be captured.
3. Confirm it is conceptual someday material, not raw issue intake, a durable rule, a pin, or active scoped work.
4. Add or update one entry in docs/scratch/future-ideas.md.
5. Preserve the user's framing and why the idea is future-facing.
6. Do not create a spike, GitHub issue, board item, or write operation unless the user is actually starting that work.