agentleFS
grace-methodgrace-method/grace-plugin/skills/project-start/SKILL.md

project-start

Skill0 starsChanged 2 months agoMITView on GitHub

Start a new GRACE-governed initiative without requiring the human to remember the opening skill sequence. Use this at the beginning of a new project or when an existing project has unclear methodology setup.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use this skill as the friendly front door for new GRACE work.

    line 12
  2. Distinctive:

    Stop at the Stage 1 gate.

    line 35
  3. Distinctive:

    Do not move into business analysis until Stage 1 is approved enough.

    line 37

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

Project Start

Use this skill as the friendly front door for new GRACE work.

It does not replace project-setup or project-definition. It routes the session through them in the expected order so the human does not need to remember the startup choreography.

Interaction Pattern

  1. Run project-setup.
    • Classify project type.
    • Set the predictability dial.
    • Choose standard structure or custom artifact mapping.
    • Scaffold starter artifacts when appropriate.
    • Get human approval for the artifact strategy.
  2. Run project-definition.
    • Identify target users and stakeholders.
    • Clarify intended value.
    • Define major task categories and initial scope intent.
    • Survey existing tools or solutions.
    • Capture thesis and guiding principles.
    • Decide whether to proceed to analysis.
  3. Stop at the Stage 1 gate.
    • Present the product-definition artifacts for human review.
    • Do not move into business analysis until Stage 1 is approved enough.

Output

Produce the same artifacts owned by the underlying skills:

  • project-setup record or artifact strategy statement
  • docs/01-project-definition/project-definition-summary.md
  • docs/01-project-definition/project-thesis-and-principles.md

Gate

Human approval is required before treating Stage 1 as complete or moving into business analysis.

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.