@dotdotgod/pi
Pi adapter for dotdotgod: project-initializer skill, shared docs scaffold, plan/archive workflow, and project loading extensions.
Package details
Install @dotdotgod/pi from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@dotdotgod/pi- Package
@dotdotgod/pi- Version
0.2.9- Published
- Jul 31, 2026
- Downloads
- 1,495/mo · 366/wk
- Author
- dotdotgod
- License
- Elastic-2.0
- Types
- extension, skill
- Size
- 216.7 KB
- Dependencies
- 2 dependencies · 5 peers
Pi manifest JSON
{
"skills": [
"./skills"
],
"extensions": [
"./extensions"
],
"prompts": [],
"subagents": {
"agents": [
"./agents"
]
}
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@dotdotgod/pi
Pi adapter for dotdotgod's docs-first project-memory workflow.
Use this package when you want Pi to initialize project memory, load bounded repository context, plan before source edits, run impact-aware checks, and archive completed work for future sessions.
Pi is the fullest dotdotgod experience: it is the only adapter that enforces Plan Mode before source edits and can gate commit, push, and publish on pending impact checks. Throughout, the maintained graph stays a compact map for targeted reads, not a giant report to consume in full.
Start Here
Install the adapter in Pi:
pi install npm:@dotdotgod/pi
Then open Pi in your repository and ask:
Initialize this project with dotdotgod.
A good first run:
- Install this package.
- Start Pi in the target repository.
- Ask Pi to initialize the project with dotdotgod.
- Review the files the initializer will create or skip.
- Run
/dd:loadto load bounded project memory. - Use
/plan <request>before implementation work.
What It Adds to Pi
| Need | Pi command or feature |
|---|---|
| Create the docs-first project scaffold | project-initializer skill |
| Load project memory without broad file reads | /dd:load (full), /dd:load:compact (compact), or /load |
| Plan safely before source/config edits | /plan and /plan <request> |
| Show execution progress | /todos |
| Review changed-file impact | /impact-check or dotdotgod_graph_impact |
| Improve docs clarity | document-clarify skill |
| Delegate analysis or implementation work | bundled pi-subagents resources |
Project Initializer
The bundled project-initializer skill creates or normalizes this memory surface:
AGENTS.md # canonical working rules for agents
CLAUDE.md # thin Claude Code pointer to AGENTS.md
CODEX.md # thin Codex pointer to AGENTS.md
dotdotgod.config.json # complete editable default project policy
docs/
README.md # project documentation map
spec/README.md # behavior, requirements, product truth
arch/README.md # architecture, conventions, boundaries
test/README.md # verification strategy and smoke tests
plan/README.md # active local plans, ignored by git
archive/README.md # completed-work history map, ignored by git
The package includes @dotdotgod/cli as a runtime dependency. Pi extensions prefer a source-checkout CLI when present, then the package-local CLI, then a global dotdotgod fallback. The initializer also includes a shell fallback and generated canonical config template for constrained environments.
Planning Workflow
/plan
Use /plan when a request may lead to source or config changes. Plan Mode keeps implementation mutations blocked until there is a durable plan under docs/plan/<task-slug>/README.md and the user chooses to execute it.
Plan Mode helps Pi:
- load relevant project memory,
- write or update active plan docs,
- track execution steps with
[DONE:n]markers, - remind agents to run impact checks after source/config edits,
- archive completed plans under
docs/archive/plan/.
Loading and Impact Checks
/dd:load renders shared Markdown paths as a prefix-compressed documentation tree, excluding plan/archive local memory by default. Without arguments it expands through directory depth 5; with arguments it runs dotdotgod query for up to 30 local multilingual E5 results and renders the tree through depth 3.
/impact-check and the dotdotgod_graph_impact tool use the maintained graph to surface related specs, tests, docs, commands, source, and config after a change. Pi can remind the agent to run impact checks and can block commit, push, or publish commands until pending impact checks pass.
Included Resources
project-initializerskilldocument-clarifyskillplan-modeextensionload-projectextensionpi-subagentswrapper resources- package-local
@dotdotgod/clidependency
If standalone pi-subagents is already installed, the wrapper avoids duplicate dotdotgod-provided tool, skill, and prompt resources.
Local Development
pi install /path/to/dotdotgod/packages/pi
pnpm --filter @dotdotgod/pi run verify
pnpm --filter @dotdotgod/pi run pack:dry-run
Learn More
See the root README, Context curation, Context mechanics, Memory area config, and Traceability config.
Compared with Graphify-Style Memory
The Pi adapter focuses on workflow. It initializes the project-memory scaffold, loads a depth-bounded documentation map with optional focused query results, plans before source edits, checks changed-file impact, and archives completed work for future sessions. The graph is a compact map for targeted reads, not a giant report for agents to consume in full.