agentleFS
Sign inStart free
VinayKhandiaVinayKhandia/no-slop/skills/planner/SKILL.md

planner

Skill1 starsChanged 11 days agoMITView on GitHub

Decomposes requirements into atomic task chunks and maintains the central TASKS.md tracking board.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use executor, debugger and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MooseDesign1Skill

    executor

    Main executor agent. Triggered by /executor, or natural language such as: "build this feature", "execute the feature", "start building", "map the codebase", "scan the code", "resume building", "continue the build", "dev status", "where are we on development", "what's built". Do NOT trigger for /planner, /plan:project, /plan:feature, /plan:status, /product-designer, /pd:*, /ds-designer, /ds-*.

    Also in 3 projects that use this

  • JohnJBorenSkill

    debugger

    Systematic debugging workflows, root cause analysis, and troubleshooting patterns

    Also in 3 projects that use this

  • JetBrainsSkill

    review-plan

    Manually re-run the autonomous plan review (Phase 2 — consistency + structural). The same review runs automatically as the first phase of /execute-tracks; this command is for re-runs after inline replanning or whenever the plan needs explicit re-validation. TRIGGER when: user asks to re-validate the plan after inline replanning; user requests explicit plan review outside /execute-tracks. SKIP: /execute-tracks already running State 0 in this session (autonomous Phase 2 path will fire) — do not double-run.

    Also in 3 projects that use this

  • Harut8Skill

    architect

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read BRIEF.md first (written by prompt-optimizer).

    line 8
  2. Distinctive:

    Strict Scope: Never create sprawling umbrella tasks.

    line 15
  3. Very specific:

    Create TASKS.md in the project root if it does not exist.

    line 26
  4. Very specific:

    Update TASKS.md immediately before starting a chunk (set status to in_progress).

    line 43
  5. Very specific:

    Update TASKS.md immediately after completing the reviewer loop (set status to done, record brief notes or file paths created).

    line 44
  6. Distinctive:

    If new work is discovered during implementation, insert new rows rather than expanding existing task scopes.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 30 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

Planner

Read BRIEF.md first (written by prompt-optimizer). Derive chunks from its acceptance criteria and keep each chunk tied to one criterion.

Decompose the optimized specification into discrete, manageable execution chunks and record them in TASKS.md.

Decomposition Rules

  1. Atomic Chunks: Each chunk must represent an independent, testable increment that can be executed in a single focused turn or by a single worker.
  2. Strict Scope: Never create sprawling umbrella tasks. If a task touches both database and UI, split it into database schema, API handler, and UI component chunks.
  3. Role Assignment: Assign every chunk to one specific role:
    • frontend: User interface, client state, styling, client-side routing.
    • backend: Business logic, core server algorithms, background routines.
    • database: Schema definitions, migrations, seed data, queries.
    • api: Network endpoints, request validation, serialization, RPC/REST routes.
    • flex: Build configuration, integration glue, documentation, tooling.
  4. Dependency Sequencing: Order tasks so foundational chunks (DB, models) precede dependent chunks (endpoints, UI views). Identify files each chunk touches to allow serialization of shared files.

Managing TASKS.md

Create TASKS.md in the project root if it does not exist. Use the following schema:

IDChunk DescriptionRoleStatusNotes
T-01Create database schema and migrationdatabasependingtouches schema.sql
T-02Implement user authentication endpointapipendingtouches routes/auth.js
T-03Build login form componentfrontendpendingtouches components/LoginForm.jsx

Status States

  • pending: Waiting to be worked on.
  • in_progress: Actively being executed by assigned role.
  • in_review: Under reviewer audit.
  • done: Audited, verified, and complete with teach note recorded.
  • blocked: Cannot proceed due to unmet upstream dependency.

Maintenance Protocol

  1. Update TASKS.md immediately before starting a chunk (set status to in_progress).
  2. Update TASKS.md immediately after completing the reviewer loop (set status to done, record brief notes or file paths created).
  3. If new work is discovered during implementation, insert new rows rather than expanding existing task scopes.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free