agentleFS
clairelily2020clairelily2020/creator-workflows/skills/long-term-plan/SKILL.md

long-term-plan

Skill0 starsChanged 21 days agoMITView on GitHub

Help users create and manage long-term project plans by clarifying goals, milestones, tasks, dependencies, and schedule. Use for founder goals, content plans, learning plans, product launches, growth programs, or research projects.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use this when the user needs to turn a large goal into a practical plan.

    line 8
  2. Distinctive:

    Do not make a plan without a time window.

    line 88
  3. Distinctive:

    Do not create vague tasks like "work on marketing."

    line 89
  4. Distinctive:

    Keep the first week concrete.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Long-Term Plan

Use this when the user needs to turn a large goal into a practical plan.

Workflow

1. Clarify The Goal

Ask:

  • What outcome should exist at the end?
  • What is the time window?
  • What is the starting point?
  • What constraints matter?
  • What would make the plan fail?

2. Define Milestones

Suggest 3 to 5 milestones.

Each milestone should have:

  • clear output
  • owner if known
  • target date
  • dependencies
  • success signal

3. Break Milestones Into Tasks

For each milestone, create tasks with:

  • action-oriented title
  • expected output
  • due date or sequence
  • estimated effort
  • dependency
  • whether the user or agent can do it

4. Confirm The Plan

Show:

  • milestone list
  • task count
  • critical path
  • next three actions
  • unresolved risks

Output

## Plan: {goal}

Time window:
{dates}

Outcome:
{end state}

Milestones:
1. {milestone} - output: {output} - due: {date}
2. ...

Tasks:
| Task | Output | Owner | Due | Depends on |
| --- | --- | --- | --- | --- |

Critical path:
{sequence}

Next three actions:
1. {action}
2. {action}
3. {action}

Risks:
- {risk}

Rules

  • Do not make a plan without a time window.
  • Do not create vague tasks like "work on marketing."
  • Keep the first week concrete.
  • Surface dependencies instead of hiding them.

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.