agentleFS
dominionismdominionism/Playbook/skills/init/SKILL.md

init

Skill0 starsChanged 2 months agoMITView on GitHub

Bootstrap the project's Context and Memories directories with non-destructive templates. Use when the user explicitly asks to initialize Playbook's project-memory structure; create missing paths and never overwrite existing content.

137 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • gaebalaiSkill

    codex-system

    PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

    Also in 3 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 125 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Idempotent: If any path already exists, skip it.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 125 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

Bootstrap this project's documentation structure. Run this once at the start of a project. All other commands expect this structure to exist — /init creates it so they don't have to.


Process

  1. Resolve the project root:
    git rev-parse --show-toplevel
  2. Create the directory structure under <project-root>/:

    <project-root>/
    ├── Context/
    │   ├── Glossary.md
    │   ├── Research/
    │   │   └── Research.md
    │   ├── ADR/
    │   └── Plans/
    └── Memories/
  3. Glossary.md — create from this template. Replace {Project Name} with the actual project name (from package.json "name", repo name, or directory name — whichever is most specific):

    # {Project Name}
    
    {A one or two sentence description of what this context is and why it exists.}
    
    ## Language
    
    <!-- Terms are added by /grill as they crystallize during grilling sessions. -->
  4. Context/Research/Research.md — create from this template. Create the Context/Research/ directory first:

    # Research: {Project Name}
    
    > Last updated: {{date}} (comprehensive)
    
    ## What is this?
    <!-- Filled by /research -->
    
    ## Architecture
    <!-- Filled by /research -->
    
    ## Domain Model
    <!-- Filled by /research -->
    
    ## Patterns
    <!-- Filled by /research -->
    
    ## Relevant ADRs
    <!-- Filled by /research -->
    
    ## Open Questions
    <!-- Filled by /research -->
  5. Context/ADR/ — empty directory. ADRs are created by /grill when architectural decisions crystallize.
  6. Context/Plans/ — empty directory. Implementation plans are created by /blueprint.
  7. Memories/ — empty directory. Session handoffs are created by /handoff.

Rules

  • Idempotent. If any path already exists, skip it. Never overwrite existing files.
  • Don't fill in content. The template is structural scaffolding. /research fills in Context/Research/Research.md; /grill fills in Glossary.md and ADR/; /blueprint fills in Plans/.
  • Report what you did. List exactly what was created vs what already existed.

Workflow

Before this command: none. /init is the very first thing you run in a new project.

After this command:

  • /research to map the codebase — will populate Context/Research/Research.md
  • /grill will populate Glossary.md and ADR/
  • /blueprint will populate Plans/
  • /handoff will populate Memories/

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.