Skip to content
Skills Library
Management & product · Planning

aim

/aim

Define the next milestone of a trajectory project: take an idea, bullet points, or an example (or propose the next feature yourself when invoked empty), scout the current project state via subagents, and write milestones/NNNN-slug.md covering the outcome, the decisions to make before breakdown, and what needs to be proven. Trigger on "/aim", "next milestone", "let's aim at…", "what should we build next", or when the user hands over a feature idea to target. Do NOT trigger for task-level capture (that's /enrich or /supplement) or for questions about existing milestones (answer those with backlo

Repository
skills ↗
Licence
MIT
Last repository change
22.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Define the next milestone of a trajectory project: take an idea, bullet points, or an example (or propose the next feature yourself when invoked empty), scout the current project state via subagents, and write milestones/NNNN-slug.md covering the outcome, the decisions to make before breakdown, and what needs to be proven. Trigger on "/aim", "next milestone", "let's aim at…", "what should we build next", or when the user hands over a feature idea to target. Do NOT trigger for task-level capture (that's /enrich or /supplement) or for questions about existing milestones (answer those with backlo

Triggers from the description

next milestoneletwhat should we build next

Arguments

/aim <optional idea, bullet points, or example for the next milestone>
Original author description

Define the next milestone of a trajectory project: take an idea, bullet points, or an example (or propose the next feature yourself when invoked empty), scout the current project state via subagents, and write milestones/NNNN-slug.md covering the outcome, the decisions to make before breakdown, and what needs to be proven. Trigger on "/aim", "next milestone", "let's aim at…", "what should we build next", or when the user hands over a feature idea to target. Do NOT trigger for task-level capture (that's /enrich or /supplement) or for questions about existing milestones (answer those with backlo

How it works

  1. Step 1: Scout
  2. Step 2: Shape the milestone (brief dialogue)
  3. Step 3: Persist
  4. Wrap-up
Original SKILL.md headings · 52 lines, 599 words
SKILL.md preview
---
name: aim
description: >
  Define the next milestone of a trajectory project: take an idea, bullet points, or an
  example (or propose the next feature yourself when invoked empty), scout the current
  project state via subagents, and write milestones/NNNN-slug.md covering the outcome, the
  decisions to make before breakdown, and what needs to be proven. Trigger on "/aim", "next
  milestone", "let's aim at…", "what should we build next", or when the user hands over a
  feature idea to target. Do NOT trigger for task-level capture (that's /enrich or
  /supplement) or for questions about existing milestones (answer those with backlog.sh).
argument-hint: <optional idea, bullet points, or example for the next milestone>
model: opus
allowed-tools: Read, Glob, Grep, Edit, Write, Bash, Agent, AskUserQuestion
---

# Aim — The Next Target

> For the full workflow this skill belongs to, see [workflow-overview.md](../_shared/workflow-overview.md).

The user's argument, if any: `$ARGUMENTS` — an idea, a bunch of bullet points, or an example of what the next milestone should achieve. If empty, form your own suggestion for the next feature to go for: read `VISION.md`, run `../_shared/scripts/board.sh`-equivalent `bash ../_shared/scripts/backlog.sh board` (relative to this skill's directory) and `backlog.sh milestone-ready`, and propose the target that most advances the vision from the current state — the user vetoes or redirects before you proceed. Put that proposal up as an `AskUserQuestion` with the 2–4 candidate targets you considered as options (your recommendation first, each description naming what it advances and what it defers) rather than a single take-it-or-leave-it sentence.

A milestone is a **grouping and labelling device** for tasks — never a barrier or synchronization point. Your output is one milestone file that `/decide` and `/enrich` can pick up without re-deriving anything.

## Step 1: Scout

Spawn the `aim-scout` subagent with the idea, the repo root, and the path to `backlog.sh`. It returns the current state relevant to the idea, overlaps with the existing backlog, candidate unknowns (decisions to make), candidate proof items, and blockers — without the raw file reads ever landing in this session. For a trivial or greenfield idea where there is nothing to scout, skip it and say so.

## Step 2: Shape the milestone (brief dialogue)

Synthesize the idea + scout report and confirm with the user — one focused exchange, not a re-interview:

- **Outcome** — what this milestone achieves, its outcome and benefit, in vision vocabulary.
- **Decisions to make** — the decisions the user needs to make before breakdown and implementation can start (from the scout's unknowns + your own reading). Each as a one-line checkbox item.
- **Needs proving** — the risky assumptions this milestone stands on that only running code can demonstrate. Each as a one-line checkbox item. These two lists are the milestone's contract with `/decide` (which turns them into decision records and back-references them) and `/land` (which clears the proofs).

Surface scout-reported overlaps with open milestones/tasks now — the user may want to fold, re-scope, or proceed anyway. That is a closed set: ask it with `AskUserQuestion` (one question per overlap; options *fold into the existing milestone* / *narrow this milestone to the remainder* / *proceed as scoped*), and keep the shaping of outcome, decisions, and proof items themselves in prose — they are open discovery, and options would flatten them. See [Asking the user](../_shared/workflow-overview.md#asking-the-user).

## Step 3: Persist

Create the file: `bash ../_shared/scripts/backlog.sh new milestone <slug> <title>`, then fill the body via Edit:

```markdown
## Outcome
<what it achieves, outcome and benefit>

## Decisions to make
- [ ] <one-line decision item>

## Needs proving
- [ ] <one-line proof item>

## Breakdown
<left empty — /enrich fills it with the coverage map>

## Landing
<left empty — /land fills it>
```

Leave `## Breakdown` empty but present: it is the coverage map `/enrich` writes (one line per element of the outcome → the tasks covering it), and `milestone-ready` treats a milestone that has tasks but no coverage map as OPEN. Do not pre-fill it with guesses — breakdown is `/enrich`'s job.

Run `bash ../_shared/scripts/backlog.sh check`. Do **not** commit — this skill runs in the foreground; leave the written file for the user to review and commit (`/commit`).

## Wrap-up

Show the board (`backlog.sh board`). Point at the next move: `/decide` if the milestone has open decision items (it usually does — that gate blocks `/enrich`), otherwise `/enrich` directly.

Versions

The database has no other skills named aim.

Database snapshot: 13.11.2026 · package version 4650ea1adce6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100enrich
    Break a trajectory milestone down into well-shaped tasks: a dialog that ticks the boxes of the next (or given) milestone and persists tasks/NNNN-slug.md files, each with a plan, decision/documentation references, complexity, dependencies, acceptance criteria, and proves links…
  • 90kickoff
    Start a trajectory project (or revise its vision): a Socratic interview about users and their needs, what success looks like, hard constraints/invariants, and the domain vocabulary, wrapped up as VISION.md with an explicit ## Vocabulary section. Trigger on "/kickoff", "start a…
  • 100ijfw-complete-milestone
    Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship milestone', 'wrap milestone', 'complete milestone <id>', /ijfw-complete-milestone.
  • 92gsd-complete-milestone
    Use when every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version.
  • 95track-milestone
    Track and manage project milestones, deliverables, and deadlines. Use when user mentions "milestone", "deadline", "deliverable", "release", "target date", or wants to track major project achievements and dependencies between milestones.
  • 100ijfw-new-milestone
    Use when the user says: 'new milestone', 'next milestone', 'plan milestone', 'start milestone', 'begin v1.2', 'kick off next release', 'next chapter', 'next campaign wave', 'next design tier', /ijfw-new-milestone

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.