agentleFS
Sign inStart free
elfrostelfrost/ai-patchlab/.agents/skills/ez-project-workflow/SKILL.md

ez-project-workflow

Skill1 starsChanged 30 days agoMITView on GitHub

Apply the EzProject operating workflow to any coding task in this repository or an EzProject-generated project. Use for implementation, debugging, refactoring, planning, or review work when Codex should read shared project context, follow PRP discipline, and keep ROADMAP, DECISIONS, AGENTS, README, and CLAUDE in sync.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill as the default operating guide for work inside an EzProject repository.

    line 8
  2. Very specific:

    Read ROADMAP.md and DECISIONS.md.

    line 12
  3. Very specific:

    Check PRPs/ and INITIAL.md when the task is feature-related.

    line 13
  4. Very specific:

    Read examples/ before implementing new patterns.

    line 14
  5. Very specific:

    If this is the template repo, use template/examples/.

    line 15
  6. Distinctive:

    If CLAUDE.md exists, treat it as a sibling runtime document that must stay aligned with structural and workflow changes.

    line 16
  7. Distinctive:

    Prefer existing project patterns over new abstractions.

    line 26
  8. Distinctive:

    Keep file paths and references concrete.

    line 27
  9. Distinctive:

    Do not leave PRPs, docs, or runtime instructions stale.

    line 28
  10. Very specific:

    When the repo contains both .claude/ and .agents/, preserve parity instead of merging the systems together.

    line 29

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

EzProject Workflow

Use this skill as the default operating guide for work inside an EzProject repository.

Workflow

  1. Read AGENTS.md first.
  2. Read ROADMAP.md and DECISIONS.md.
  3. Check PRPs/ and INITIAL.md when the task is feature-related.
  4. Read examples/ before implementing new patterns. If this is the template repo, use template/examples/.
  5. If CLAUDE.md exists, treat it as a sibling runtime document that must stay aligned with structural and workflow changes.
  6. Validate changes with the smallest useful loop before moving on.
  7. Finish with documentation sync:
    • ROADMAP.md
    • DECISIONS.md when architecture changed
    • AGENTS.md
    • CLAUDE.md if present
    • README.md if setup or usage changed

Rules

  • Prefer existing project patterns over new abstractions.
  • Keep file paths and references concrete.
  • Do not leave PRPs, docs, or runtime instructions stale.
  • When the repo contains both .claude/ and .agents/, preserve parity instead of merging the systems together.

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