agentleFS
yuanJewelyuanJewel/skills/plan-outline/SKILL.md

plan-outline

Skill2 starsChanged 4 days agoMITView on GitHub

When writing an overall proposal, solution outline or boundary design, turn the request into goals, scope, direction, external agreements, acceptance and open decisions. Use for the proposal stage before detailed design; implementation detail belongs to plan-design, independent proposal review to plan-review, and ordinary Q&A needs no proposal.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈17

    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:

    Leave file-level implementation choices and wording to the detailed designer or implementer within the agreed boundaries.

    line 11
  2. Distinctive:

    Read the task entry, original request, later instructions, existing decisions and the relevant project evidence.

    line 16
  3. Distinctive:

    Keep these inputs distinct:

    line 17
  4. Distinctive:

    If the intended result is unclear, record the alternatives and pause only the dependent design.

    line 33
  5. Distinctive:

    If a claimed existing fact cannot be checked within read permission, mark it unverified and identify the affected decision.

    line 36
  6. Distinctive:

    Expose real decisions: Put unresolved choices first with facts, options, trade-offs, impact and recommendation.

    line 46
  7. Distinctive:

    Use the requirements and proposal format and template for a new proposal.

    line 50
  8. Distinctive:

    Use the project's established equivalent format directly when it already holds the same information.

    line 52
  9. Distinctive:

    Document splitting and standing-document presentation belong to documentation-authoring.

    line 53
  10. Distinctive:

    Read the original request again and verify:

    line 57
  11. Distinctive:

    Every required result appears in scope and has an acceptance point.

    line 59
  12. Distinctive:

    Every proposed capability has a requirement basis or is labelled as a suggestion.

    line 60
  13. Distinctive:

    Use plan-review for independent proposal or outline review.

    line 72
  14. Distinctive:

    After the required decisions are settled, plan-design expands the approved proposal into detailed design when that work is requested.

    line 74
  15. Distinctive:

    Do not ask again for decisions already covered by the current authorisation.

    line 75
  16. Distinctive:

    No directly adopted external source.

    line 88
  17. Distinctive:

    No third-party license file is required.

    line 92

≈ “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

Overall proposals and boundary design

Explain what should change, why that direction solves the problem and how the result will be judged. Leave file-level implementation choices and wording to the detailed designer or implementer within the agreed boundaries. A complex proposal may be long; length alone is no reason to omit a necessary boundary or pre-write the implementation.

Establish the basis

Read the task entry, original request, later instructions, existing decisions and the relevant project evidence. Keep these inputs distinct:

  • The requester's words, with source and time where supplied.
  • The task author's interpretation of the problem and desired outcome.
  • Decisions already made, their source and applicable scope.
  • Verified facts, applicable versions and evidence locations.
  • Assumptions and missing information that affect a decision.

An interpretation is not a new requirement. Existing complete proposals are reused and only actual gaps are filled by their authorised writer. A proposal request does not authorise implementation, publishing or changed project policy.

Choose the direction and boundaries

  1. State the problem and result. Identify the affected reader or user, the current limitation and an observable desired result. Separate the proposed solution in the request from the underlying need without discarding either. If the intended result is unclear, record the alternatives and pause only the dependent design.
  2. Draw the scope. State included and excluded behaviour, data, actors and environments. Locate existing capabilities before proposing replacements. If a claimed existing fact cannot be checked within read permission, mark it unverified and identify the affected decision.
  3. Explain the direction and structure. Show the components, responsibilities and major flow after the change. Compare alternatives only where the choice affects requirements, safety, compatibility, cost or acceptance. Give reasons for the selected direction and keep author suggestions visibly separate from agreed scope.
  4. State external agreements. Define the behaviour that crosses a boundary: who supplies what, observable output, identity and permission, failure meaning and compatibility obligations. Include failure recovery and transition limits when they affect the overall direction. Detailed signatures, exact files, algorithms and executable steps belong to plan-design after this direction is settled.
  5. Make acceptance decidable. Map every included requirement to an observable acceptance point. State what evidence would distinguish the intended behaviour from a plausible failure, including relevant negative and recovery paths. Distinguish a planned check from an actual result.
  6. Expose real decisions. Put unresolved choices first with facts, options, trade-offs, impact and recommendation. Record the dependent work and what can continue independently. A written default is a recommendation and does not manufacture approval.

Use the requirements and proposal format and template for a new proposal. Its structure preserves the original request and gives the decider a single entry. Use the project's established equivalent format directly when it already holds the same information. Document splitting and standing-document presentation belong to documentation-authoring.

Check the result

Read the original request again and verify:

  • Every required result appears in scope and has an acceptance point.
  • Every proposed capability has a requirement basis or is labelled as a suggestion.
  • The structure and external agreements use the same terms and compatible boundaries.
  • Existing facts have evidence; unknowns remain visible with their consequences.
  • Safety, old consumers and recovery constraints survive the change.
  • The proposal leaves implementation choices that the executor may reasonably decide.

A proposal about reusable methods uses only generic capabilities and synthetic examples. Local paths, machine policy, organisation rules and deployment facts are project inputs rather than universal methods.

Deliver and recover

Deliver the proposal location and version, requirement basis, selected direction, acceptance coverage and unresolved decisions. Use plan-review for independent proposal or outline review. Review comments and an author's checks are not the decider's approval. After the required decisions are settled, plan-design expands the approved proposal into detailed design when that work is requested. Do not ask again for decisions already covered by the current authorisation.

Conflicting instructions or missing decisive evidence -> preserve the verified proposal and identify exactly what is blocked. A changed requirement -> record its source and which earlier decisions or acceptance points it invalidates; do not silently rewrite approval history. Progress, continuation and transfer of write responsibility belong to context-handoff. Historical retention belongs to archive-maintenance.

Routine structure may use normal/medium; conflicting requirements or complex boundary decisions suit normal/high. Grade words map to actual execution configuration through the project resource mapping. Tools, independent sessions and environments are host limits supplied by project configuration; a proposal grants no dispatch rights.

Sources

  1. No directly adopted external source; the proposal method and transferred requirements format are library-authored.
  2. Own-authored overall-direction and boundary method; the requirements format preserves decision-first presentation and verbatim request provenance. General design-doc, RFC and decision-record conventions inform the format; no external text is copied. Detailed implementation planning, execution tracking and host-specific governance are excluded.
  3. No third-party license file is required; the root LICENSE applies.

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.