agentleFS
wheslleyrimarwheslleyrimar/BuildCLI-Agents/.claude/skills/focus/SKILL.md

focus

Skill3 starsChanged 11 days agoMITView on GitHub

Move the active blueprint pointer without re-running brief. Lists blueprints or switches to one. Updates .buildcli/active.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read each one's header comments for name, kind, created date.

    line 25
  2. Very specific:

    Run .buildcli/runtime/bcx active <path> — it validates and writes the pointer.

    line 37
  3. Distinctive:

    Read the blueprint's name and stage.

    line 38
  4. Very specific:

    Never create or delete a blueprint.

    line 69
  5. Distinctive:

    Always print the stage after switching, so the user knows where to resume.

    line 71

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Focus

Arguments

(optional) Blueprint slug or path. Omitted → lists everything available.

Output

Updated .buildcli/active + confirmation.

Goal

Change which blueprint is live — for juggling features in parallel, or picking back up something started last week.

Steps

No arguments — list mode

  1. Scan blueprints/features/ and blueprints/defects/ for directories containing a brief.md.
  2. Read each one's header comments for name, kind, created date.
  3. Mark the currently active blueprint (from .buildcli/active) with ←.
  4. Show per-blueprint progress: which of brief / shape / worklist / audit exist.
  5. Invite the user to pass a slug to switch.

With an argument — switch mode

  1. Resolve the target:
    • Bare slug → check blueprints/features/<slug>/, then blueprints/defects/<slug>/.
    • Argument already carries a features/ or defects/ prefix → use it directly.
    • Nothing matches → list what exists and ask again.
  2. Confirm brief.md is present in the target directory.
  3. Run .buildcli/runtime/bcx active <path> — it validates and writes the pointer.
  4. Read the blueprint's name and stage; confirm the move.

Output — list mode

Blueprints:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 features/
   checkout-flow   [brief ✓ shape ✓ worklist ✓ audit –]  ← active
   user-auth       [brief ✓ shape ✓ worklist – audit –]
   dashboard-v2    [brief ✓ shape – worklist – audit –]

 defects/
   payment-safari  [brief ✓ shape – worklist – audit –]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Run: /focus user-auth

Output — switch mode

Active blueprint moved:
  from: blueprints/features/checkout-flow
  to:   blueprints/features/user-auth

Stage: shape  (worklist not generated yet)
Next step: /worklist

Rules

  • Never create or delete a blueprint. The only file this command writes is .buildcli/active.
  • Slug present under both features/ and defects/ → ask which one.
  • Always print the stage after switching, so the user knows where to resume.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.