# Iteration Directions

Skill: `geo-content-brief-skill`

- Maturity tier: `scaffold`
- Selection rule: Pick the three smallest next steps that increase reliability more than they increase context cost.
- Start here: `Tighten trigger and exclusions`
- Why first: The package needs clearer near-neighbor exclusions before it grows.
- Defer for now: `Promote from scaffold to production-ready`

## Top 3 Next Moves

### 1. Tighten trigger and exclusions

- Why now: The package needs clearer near-neighbor exclusions before it grows.
- Timing: Do this first.
- Recommended actions:
  - Add 3 to 5 should-trigger and should-not-trigger examples.
- Unlocks: Cleaner routing and fewer accidental activations.
- Wait on: Wait to add broader structure until this move clearly improves reliability.

  - Refine the frontmatter description to name the recurring job and non-goals.
- Unlocks: Cleaner routing and fewer accidental activations.
- Wait on: Wait to add broader structure until this move clearly improves reliability.

  - Run a first trigger evaluation pass before expanding the package.
- Unlocks: Cleaner routing and fewer accidental activations.
- Wait on: Wait to add broader structure until this move clearly improves reliability.

### 2. Add the first execution asset

- Why now: The package is still mostly prose. Add one asset that removes repeated manual work.
- Timing: Do this after the first move lands cleanly.
- Recommended actions:
  - Move stable procedural guidance into references if users will need it repeatedly.
- Unlocks: Stronger execution quality without bloating the entrypoint.
- Wait on: Wait until the package has evidence that this extra structure is justified.

  - Create one deterministic helper script if a repeated step can be executed instead of described.
- Unlocks: Stronger execution quality without bloating the entrypoint.
- Wait on: Wait until the package has evidence that this extra structure is justified.

  - Keep the main SKILL.md compact and route-oriented.
- Unlocks: Stronger execution quality without bloating the entrypoint.
- Wait on: Wait until the package has evidence that this extra structure is justified.

### 3. Promote from scaffold to production-ready

- Why now: The first version exists; the next gain usually comes from adding the smallest useful gates.
- Timing: Do this after the first move lands cleanly.
- Recommended actions:
  - Decide whether this skill is personal, team-reused, or library-grade.
- Unlocks: A clearer path from exploratory package to maintained asset.
- Wait on: Wait until the package has evidence that this extra structure is justified.

  - Add only the gates that match that risk level.
- Unlocks: A clearer path from exploratory package to maintained asset.
- Wait on: Wait until the package has evidence that this extra structure is justified.

  - Record lifecycle metadata and review cadence once reuse becomes real.
- Unlocks: A clearer path from exploratory package to maintained asset.
- Wait on: Wait until the package has evidence that this extra structure is justified.
