agentleFS
Sign inStart free
pi247pi247/classic-PM-skills/skills/lifecycle/start-project/SKILL.md

start-project

Skill1 starsChanged 3 months agoMITView on GitHub

Orchestrate project initiation: context, stress-test alignment, charter and stakeholders, through a ready-to-plan gate. Use when kicking off a project or authorizing work.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-tests and commit.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure setup (.classic-pm/) exists or run setup-classic-pm.

    line 21
  2. Very specific:

    Ensure ORG_CONTEXT.md / PROJECT_CONTEXT.md exist.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Start project

Orchestrator - do not duplicate document templates; call the specialist skills.

Sequence

  1. Ensure setup (.classic-pm/) exists or run setup-classic-pm.
  2. Ensure ORG_CONTEXT.md / PROJECT_CONTEXT.md exist; fill via org-context / project-context as needed.
  3. /stress-test until initiation assumptions are aligned (docs mode recommended).
  4. draft-project-charter then draft-stakeholder-register.
  5. Ready-to-plan gate: charter authorized (or clear next approval), stakeholders listed, open assumptions that block planning are closed or explicitly deferred.

Output a short initiation checklist of what is done vs deferred.

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