agentleFS
Sign inStart free
modimihir07modimihir07/agentic-os/skills/project-planner/SKILL.md

project-planner

Skill209 starsChanged 3 months agoMITView on GitHub

Detailed implementation plans and spec-driven development

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-designer, security-auditor and 1 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.
  • AutumnsGroveSkill

    api-designer

    Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation

    Also in 3 projects that use this

  • nahisahoSkill

    security-auditor

    security-auditor skill

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing any significant code

    line 18
  2. Distinctive:

    Read standards/ for project conventions

    line 22
  3. Distinctive:

    Create spec document with screens and data model

    line 23

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

Project Planner

Description

Creates detailed implementation plans from high-level goals. Breaks work into bite-sized tasks with exact file paths, complete code templates, and verification steps.

When to Use

  • Starting a new feature
  • Planning a refactor
  • Spec-driven development
  • Before writing any significant code

Process

  1. Brainstorm and refine requirements
  2. Read standards/ for project conventions
  3. Create spec document with screens and data model
  4. Break into tasks (2-5 minutes each)
  5. Each task has: file path, code template, verification step
  6. Save spec and plan to context/

Output

Spec document + task plan + implementation order

Agent Assignment

  • Primary: opencode
  • Fallback: agy

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