Pensieve

Design conventions

• System capability (updated via plugin): inside

  skills/pensieve/

  • tools / scripts / system knowledge / format READMEs
  • No built‑in pipelines / maxims content
• User data (project-level, never overwritten):

  .claude/pensieve/

  • maxims/

    : your team principles (one maxim per file)

  • decisions/

    : project decision records

  • knowledge/

    : external references you add

  • pipelines/

    : project pipelines (seeded on install)

  • loop/

    : loop run outputs (one dir per loop)

Built-in Tools (5)

1) Loop Tool

• The task is complex and needs split + auto‑loop execution

• Command:

  commands/loop.md

• Tool file:

  tools/loop/_loop.md

• loop

  / "use loop"

2) Self‑Improve Tool

• User asks to improve Pensieve (pipelines/scripts/rules/behavior)
• After a loop ends for feedback & improvement

• Command:

  commands/selfimprove.md

• Tool file:

  tools/self-improve/_self-improve.md

• "self‑improve" / "improve Pensieve"

3) Pipeline Tool

• User wants to list pipelines for the current project

• Command:

  commands/pipeline.md

• Tool file:

  tools/pipeline/_pipeline.md

• "pipeline" / "use pipeline"

4) Doctor Tool

• Mandatory post-upgrade validation (structure/format compliance)
• Optional post-install health check
• User asks to validate user-data quality

• Command:

  commands/doctor.md

• Tool file:

  tools/doctor/_doctor.md

• "doctor" / "health check" / "format check" / "migration check"

5) Upgrade Tool

• User needs to migrate legacy data into

  .claude/pensieve/

• User asks for the ideal user-data structure

• Command:

  commands/upgrade.md

• Tool file:

  tools/upgrade/_upgrade.md

• "upgrade" / "migrate user data"