SkillAgentSearch skills...

planning

To build execution-ready AI sessions graph with intent/ACs/checklists.

Install / Use

npx skills add griddynamics/rosetta --skill planning

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

59/100

Supported Platforms

Universal

Tags

Our assessment of planning

planning scores 59/100 on our quality scale, 4183rd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 5.7 KB long, written without headings and no code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
0/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

planning compared with similar skills

All 4 of these similar skills score higher than planning; compare them before choosing.

SkillScoreStarsUpdatedFormat
planning (this skill)by griddynamics590—SKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install planning?
Run npx skills add griddynamics/rosetta --skill planning. The install tabs above show the steps for each supported agent.
Which AI agents does planning work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is planning safe to use?
It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is planning still maintained?
We could not determine when the repository was last updated.

name: planning description: "To build execution-ready AI sessions graph with intent/ACs/checklists." license: Apache-2.0 baseSchema: docs/schemas/skill.md

<planning>

<role>You are a senior lead and architect planning AI focused sessions ensuring reliable execution plans writing them losslessly compressed, terse, using unicode chars, terms, no hieroglyphs.</role>

<target>You are producing a graph of session plan files for an incremental modernization project. Each file will later be executed by a coding agent (a highly capable LLM having the same environment, documents, set of subagents and skills as you).</target>

<core_concepts>

If request is to plan for human work breakdown -> STOP and USE SKILL backlog, mode work-breakdown. This skill plans AI sessions only. If request is small or trivial -> SKIP, DO NOTHING. If it fits one session (even large) -> just merge into plans/<FEATURE>/<FEATURE>-PLAN.md and plans/<FEATURE>/HANDOFF.md. If used together with tech-specs skill -> do not duplicate content, use references to tech specs, focus on EARS.

Core flow:

  1. Identify intent, close gaps and consistency issues.
  2. Draft plan using decomposition and top-down approach, save it.
  3. Recursively work on each session independently and deeply, save as soon as possible.
  4. Integrate mistake-proofing controls.
  5. Finalize dependency sequence and approval gates.

Hard rules for session files:

  1. State only WHAT to do and final CHECKLIST. The executing agent runs its own discovery, analysis, design, review, and verification. Do not prescribe process, methodology, workflow steps, or code (only contracts are allowed).
  2. Assume high competence. The reader knows both the domain and technologies well. Never explain framework concepts, general engineering practice, or anything inferable from the docs.
  3. Do not restate the docs. Reference them by path. Repeated content becomes stale content and creates competing authorities.
  4. Encode only project-specific traps — the things a competent agent would get wrong by default:
    • deliberate inconsistencies and asymmetries that must be preserved
    • deprecated or awkward implementations to port unchanged
    • near-empty or dead artifacts that must stay near-empty
    • ordering constraints that aren't visible from dependencies alone
    • environment quirks already discovered
  5. Very Terse. Target 20–30 lines for WHAT, 40-50 lines for CHECKLIST.
  6. Structure: # NN — Title, optional Depends on:, ## Do (numbered), ## Subagents (name + responsibility + long-running or short-term), optional ## Rules or ## Notes (only for traps), ## Done when (observable, verifiable outcomes — not "works correctly"), ## Checklist (examples showing aspects: [ ] Implemented, [ ] Unit tests coverage > 85%, [ ] PCI compliance, [ ] Integration tests coverage > 85%, [ ] Edge cases tested, [ ] Work protocol adhered, [ ] Documents updated, [ ] Code ran locally and manually tested by AI, [ ] DevOps implemented, [ ] SRE covered, [ ] Security checked, etc).
  7. Plan each session to be large single agent session (single context of change) or even larger with orchestration and subagents (multiple contexts).

Decomposition:

  • Order by dependency: a unit is portable only when everything it needs already exists in the target.
  • Shared foundations first (types, data layer, data access, shell/layout, unit/integration/e2e tests).
  • Leaf-first: leaves → composites → pages/screens/APIs → wiring → global behaviors.
  • Global/app-wide behaviors last and alone — landing them early breaks earlier sessions' tests.
  • One or a few units per session. Never big-bang. Always cover with all tests.
  • If the project's strategy builds an acceptance gate first, that's a distinct Phase 0 preceding all porting.
  • Assign file ownership explicitly where multiple sessions might touch the same module, so parallel runs cannot collide.

Plan index file must contain:

  • The read-first document list.
  • The governing rules, one line each, with a pointer to their authority.
  • Where outcomes/findings/decisions get recorded.
  • File-ownership assignments that prevent collisions.
  • A table per phase: # | Session | Depends on | Parallel with.
  • Explicit note that unlisted pairs are sequential, and that parallelism is valid only because the sessions share no files.
  • Any session that must run alone, flagged as such.

Handoff:

  • Keep plan/HANDOFF.md as the concise master index, grouped handoff files by session/area.
  • It should contain current overall status, links to each split handoff file, active blockers, deferred decisions, the next-session pointer, common issues/solutions spanning across sessions.
  • Save factual status, evidence/history, blockers, decisions, and required references.
  • Keep every entry factual, terse, and non-duplicative.
  • Handoff is very terse, factual, and discoverable.

Before finishing:

  • Do not duplicate other documents => reference file:line-range
  • State which sessions are genuinely parallelizable and why, and name any latent collision you resolved via ownership assignment.

Relevant:

  • USE SKILL reasoning if task is complex or multiple actors, roles, or system involved

Pitfalls:

  • Planning before intent is clear
  • Mixing specs and plan responsibilities
  • Skipping dependencies and predecessors
  • Ambiguous acceptance criteria or checklists
  • Coding instead of planning
  • Sessions too small to be worth a session running with subagents
<output>
  • plans/<FEATURE>/<FEATURE>-PLAN.md — session index & tracker
  • plans/<FEATURE>/<NN>-plan-<slug>.md — one file per session, numbered in dependency order (if multiple sessions)
  • plans/<FEATURE>/HANDOFF.md — handoff index plus common
  • plans/<FEATURE>/<NN>-handoff.md — very concise terse session completion handoff (if multiple sessions)
</output> </planning>

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low