agentleFS
Sign inStart free
VoTruongDanhVoTruongDanh/Skills-Agent/.agents/skills/plan/SKILL.md

plan

Skill4 starsChanged 33 days agoMITView on GitHub

Create concrete implementation plans with milestones, task breakdowns, and estimates. Use when the user wants to plan, organize work, or create a roadmap. Triggers: plan, milestone, breakdown, roadmap, estimate, kế hoạch, lên kế hoạch, phân chia công việc.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 166 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    START: Read .ai-memory.md from project root.

    line 10
  2. Very specific:

    END: Update .ai-memory.md using Memory Compaction Rules with: plan summary, phases/tasks, key risks, and first recommended action.

    line 11
  3. Distinctive:

    If any answer is unclear, ASK before proceeding.

    line 29
  4. Distinctive:

    Prefer task sizes that can be completed and reviewed quickly.

    line 63
  5. Distinctive:

    Always read and update the memory file.

    line 65
  6. Very specific:

    After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.

    line 68
  7. Very specific:

    All code snippets and example files referenced or produced by this skill must be UTF-8 encoded.

    line 76

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

Memory Protocol

START: Read .ai-memory.md from project root. Check existing plans, milestones, project structure, tech stack, ongoing work, and past decisions. END: Update .ai-memory.md using Memory Compaction Rules with: plan summary, phases/tasks, key risks, and first recommended action.

Goal

Turn a request into an actionable plan with clear phases and tasks.

Agent Routing

  • For architecture planning → read .kiro/skills/agents/agents/project-planner.md and apply its knowledge
  • For multi-domain coordination → read .kiro/skills/agents/agents/orchestrator.md and apply its knowledge
  • For technical feasibility → read the relevant specialist agent file:
    • Backend: .kiro/skills/agents/agents/backend-specialist.md
    • Frontend: .kiro/skills/agents/agents/frontend-specialist.md
    • Database: .kiro/skills/agents/agents/database-architect.md

Socratic Gate

Before planning, verify:

  1. What is the desired outcome? (specific deliverable)
  2. What constraints exist? (time, resources, tech stack)
  3. What is already built vs needs to be built? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for project context and history.
  2. Define the objective and acceptance criteria.
  3. Break the work into phases and tasks.
  4. Note file areas, systems, or modules likely to change.
  5. Estimate complexity and highlight risky items.
  6. End with a recommended first task.
  7. Update Memory — Save plan details to .ai-memory.md.

Output format

  • Objective
  • Acceptance criteria
  • Phases (with tasks under each)
  • File areas / modules affected
  • Risks (with mitigation)
  • Recommended first action

Checklist

  • Objective clearly stated
  • Acceptance criteria defined
  • Phases broken down
  • Tasks are specific and actionable
  • Complexity estimated per task
  • Risks identified with mitigation
  • First action recommended
  • Memory file updated
  • Clean code chuẩn (Standard clean code applied)
  • Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated)

Rules

  • Plans should be specific enough to execute.
  • Prefer task sizes that can be completed and reviewed quickly.
  • Minimize blast radius: call out the smallest set of files likely to change; if scope is unclear, ASK.
  • Always read and update the memory file.

Quality Gate

After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.

Related Skills

  • /brainstorm → read .kiro/skills/brainstorm/SKILL.md — Explore options before planning
  • /create → read .kiro/skills/create/SKILL.md — Execute planned tasks
  • /orchestrate → read .kiro/skills/orchestrate/SKILL.md — Coordinate complex plans across teams

Encoding

All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include encoding: "UTF-8" in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM).

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