agentleFS
RedberryProductsRedberryProducts/synapse/.claude/skills/plan-epic/SKILL.md

plan-epic

Skill65 starsChanged 19 days agoMITView on GitHub

Plan unfinished Synapse features from the user's request, GitHub issue acceptance criteria, the current implementation, and verified SDK APIs. Use when starting an epic, enriching a future plan, or breaking a feature into implementation steps.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Kealman/cland-v0★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start with the user's request and the active GitHub issue.

    line 8
  2. Distinctive:

    Read the issue's goal, scope, acceptance criteria, and relevant discussion.

    line 12
  3. Very specific:

    Verify SDK facts against the installed/tagged source.

    line 14
  4. Very specific:

    Read config/synapse.php for current keys.

    line 16
  5. Very specific:

    Use the issue/PR for the main discussion.

    line 33
  6. Distinctive:

    Before removing a completed plan, preserve unique unfinished work in an open issue or the future backlog, record implementation/validation …

    line 35
  7. Distinctive:

    Update README/UPGRADE for behavior or migration changes, DEV for commands, and AGENTS for lasting contributor rules.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Planning a Synapse feature

Start with the user's request and the active GitHub issue. Read AGENTS.md and DEV.md for conventions and checks. Use README.md and UPGRADE.md for supported behavior and migration constraints.

Gather evidence

  • Read the issue's goal, scope, acceptance criteria, and relevant discussion. User instructions take precedence; identify unresolved contradictions rather than silently expanding scope.
  • Inspect current source and tests before proposing new helpers or abstractions. Consult closed issues and merged PRs for earlier decisions when relevant.
  • Verify SDK facts against the installed/tagged source. references/ is read-only research material and may be stale; record the version inspected. Use released APIs, not assumptions from an unreleased branch.
  • For UI work, reuse the component layers and tokens documented in AGENTS. Consult Figma only when the feature has a relevant design; record the exact design reference and distinguish it from an implementation choice.
  • Read config/synapse.php for current keys. Propose new configuration only when the feature needs it.

Write a focused plan

Scale detail to the task. A small change needs a short plan; a substantial feature should cover:

  1. Goal and scope: user-visible outcome, issue link, acceptance criteria, and explicit exclusions.
  2. Evidence and decisions: SDK version/APIs, current implementation, and material tradeoffs or uncertainties.
  3. Implementation sequence: concrete steps, affected classes/components/routes/storage, and verification for each step. Reuse existing primitives before adding new ones.
  4. Contracts and migration: request/response shapes, persistence, replay, and upgrade behavior only where changed. Synapse never modifies SDK conversation tables.
  5. Tests: map acceptance criteria to feature tests and, for UI/chat changes, browser tests. Automated browser tests use faked agents. Verify real HTTP flushing separately if streaming mechanics change.
  6. Risks and completion: unresolved decisions, relevant regression coverage, documentation updates, and the applicable gates from DEV.

For frontend work, follow the four layers in AGENTS: elements, components, composed, and pages. Identify only components actually affected, with whether each is reused, changed, or introduced. Include both themes, narrow layouts, reload, and failure/approval behavior where relevant.

Keep plans temporary

Use the issue/PR for the main discussion. Create plans/<feature>/PLAN.md only when a substantial unfinished task needs a local plan; no master roadmap or completed-plan archive is required. Keep speculative SDK ideas in SDK-OPPORTUNITIES.md until selected.

Before removing a completed plan, preserve unique unfinished work in an open issue or the future backlog, record implementation/validation in the PR, and update maintained documentation. Remove unreferenced plan assets with the plan. Git history and merged PRs retain completed work.

Definition of done

  • The implementation meets the agreed acceptance criteria.
  • composer check passes; composer test:e2e passes when frontend/chat behavior changes.
  • Rebuild committed dist/ when frontend source changes.
  • Update README/UPGRADE for behavior or migration changes, DEV for commands, and AGENTS for lasting contributor rules.
  • Describe validation and remaining limitations in the PR without exposing credentials or local application data.

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.