agentleFS
Sign inStart free
pi247pi247/classic-PM-skills/skills/setup/setup-classic-pm/SKILL.md

setup-classic-pm

Skill1 starsChanged 3 months agoMITView on GitHub

Configure Classic PM Skills for this workspace: tool surface, status vocabularies, document and context paths, and optional light process notes. Use once when adopting the pack or when paths/tools change.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Create or update tool-agnostic config under .classic-pm/ so every skill knows where documents live and which vocabulary to use.

    line 17
  2. Very specific:

    Default tool surface: local-markdown.

    line 33
  3. Very specific:

    After setup, offer to create empty ORG_CONTEXT.md / PROJECT_CONTEXT.md / DECISIONS.md at the configured paths.

    line 36

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

Setup Classic PM Skills

Create or update tool-agnostic config under .classic-pm/ so every skill knows where documents live and which vocabulary to use.

Create

.classic-pm/
  config.md       # tool surface
  vocabularies.md # statuses/labels
  paths.md        # context + document locations
  process.md      # optional predictive / hybrid notes

See examples/.classic-pm/ in this repo for starters.

Rules

  1. Default tool surface: local-markdown.
  2. Skills read paths from config - never hardcode a vendor UI.
  3. Deep Jira/ADO/Asana/Notion/MS Project connectors are out of v1 unless paths + vocabularies are enough.
  4. After setup, offer to create empty ORG_CONTEXT.md / PROJECT_CONTEXT.md / DECISIONS.md at the configured paths.

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