JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 649
  • Score
    100M100P100Q99253F
  • License MIT

Repo-local project memory for humans and AI agents.

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (benjamin-docs) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    benjamin-docs

    Local project memory for humans and AI agents.

    npm package

    benjamin-docs turns useful chats and project work into project docs.

    It keeps decisions, plans, open questions, and handoff notes in Markdown files inside your project.

    No cloud. No dashboard. No transcript dump.

    Why It Exists

    Chats are great for thinking.

    They are bad at becoming project memory.

    benjamin-docs saves the useful parts: decisions, plans, open questions, and handoff notes.

    So the next person or agent can start with context instead of asking you to explain everything again.

    Install

    pnpm add -g benjamin-docs
    benjamin-docs install-skill
    benjamin-docs help

    Also works as a project dependency:

    pnpm add benjamin-docs

    Need npm or one-off runs?

    npm install -g benjamin-docs
    npx benjamin-docs

    install-skill installs the bundled agent skill for local agents:

    ~/.agents/skills/benjamin-docs/
    ~/.codex/skills/benjamin-docs/
    ~/.claude/skills/benjamin-docs/
    ~/.cursor/skills/benjamin-docs/

    Codex, Cursor, and Claude Code can use the shared ~/.agents/skills install.

    Claude Desktop / Claude.ai uses uploaded skills:

    benjamin-docs package-skill

    Then upload ~/Downloads/benjamin-docs-skill.zip in Claude.

    Main Commands

    Start here:

    benjamin-docs init
    benjamin-docs ready
    benjamin-docs help

    init creates project memory. ready checks setup, validation, and docs quality. help shows the simple path.

    For the full command drawer:

    benjamin-docs commands

    In an interactive terminal, choose with Up/Down or type a number, then press Enter to run the selected command.

    Frequent users can use the short alias:

    bd ready

    Turn A Chat Into Project Memory

    If you only have a chat and no project folder yet, ask your agent:

    Use the benjamin-docs skill to create a project from this chat.

    The agent should suggest:

    ~/Documents/Benjamin Docs/<Project Name>

    It should ask before creating files. After you confirm, it creates a local project with:

    README.md
    benjamin-docs/
    .benjamin-docs/

    The skill runs planning setup, writes the starter project memory, and checks whether the project is ready. For the exact agent prompt:

    benjamin-docs chat-project

    Use It In An Existing Project

    For an existing app or codebase:

    benjamin-docs init

    In an obvious codebase, init sets up codebase memory and repo-local agent guidance automatically. Existing AGENTS.md files are preserved; Benjamin-owned sections are marked so they can be updated without rewriting the rest of the file.

    Then ask your agent:

    Capture the current project baseline with benjamin-docs.

    When the docs are captured:

    benjamin-docs ready

    Use mode flags only when you want to be specific:

    benjamin-docs init --mode planning
    benjamin-docs init --mode codebase
    benjamin-docs init --mode feature --feature <slug>
    benjamin-docs init --no-agent-contract
    benjamin-docs next

    Check Readiness

    benjamin-docs ready

    ready runs the full gate: setup, validation, and docs quality.

    If ready fails, use benjamin-docs commands to find lower-level diagnostics such as validation, review, or doctor checks.

    What It Creates

    benjamin-docs/
      project/
      handoff/
      engineering/
      features/
      releases/
    
    .benjamin-docs/

    benjamin-docs/ is for people and agents.

    .benjamin-docs/ is metadata for validation, scopes, anchors, and exports.

    Existing docs/ folders are left alone unless you explicitly configure otherwise.

    More Commands

    Use benjamin-docs commands when you need advanced setup, diagnostics, exports, scope commands, or skill packaging.

    Useful advanced examples:

    benjamin-docs anchor add homepage pages/index.js
    benjamin-docs anchor list
    benjamin-docs scope create feature checkout-redesign
    benjamin-docs init --help

    Local Development

    git clone https://github.com/msiksnis/benjamin-docs.git
    cd benjamin-docs
    pnpm install
    pnpm check

    Before publishing:

    pnpm run release:check
    tmpdir=$(mktemp -d)
    pnpm pack --pack-destination "$tmpdir"
    npm publish "$tmpdir"/benjamin-docs-*.tgz --access public

    Contributing

    Keep it local-first.

    Keep docs readable by non-programmers.

    Keep agent workflows explicit.

    Avoid magic that writes outside the project unless the user runs a clear command.