Skip to content

Adding in persistent knowledge base and milestone thinking - #11

Draft
KennySmash wants to merge 2 commits into
Ovid:mainfrom
KennySmash:main
Draft

Adding in persistent knowledge base and milestone thinking#11
KennySmash wants to merge 2 commits into
Ovid:mainfrom
KennySmash:main

Conversation

@KennySmash

Copy link
Copy Markdown

Why

Persistent repository-native memory is needed so humans, lead agents, and sub-agents can share context across sessions without reloading a long journal or inventing answers to questions already settled. Stable architecture stays in docs/; mutable working knowledge lives under kb-brain/.

What

paad:kb-brain

  • Initializes kb-brain/ (no bulk ingest of docs/)
  • Focused task workspaces (minimal / standard / strict) with index-first retrieval
  • Autonomous atomic writes for findings, questions, failures, conflicts, handoffs, improvements, and tech-debt
  • Lead/human-only authority for scope, assignments, confirmed decisions, and closure
  • Closure sealing via SEAL.json (SHA-256); post-close corrections only via amendments/
  • Stdlib tooling: scripts/kb_brain.py + Make targets (kb-index, kb-new, kb-check, …)

paad:brief-ruminate

  • Expands one human-owned brief milestone into a candidate spec at review-needed
  • Stops before approval, planning, or implementation
  • Only a human may mark approved-spec
  • Does not auto-run pushback, alignment, or agentic-review

Explicit non-goals

  • Existing PAAD skills are not behaviourally modified (help/README listings only)
  • No automatic KBB wiring into other skills
  • Plugin version left at 1.24.1; changelog under [Unreleased] (bump is a separate /release)

Tests / validation

  • make export && make test (includes claude plugin validate, digraph/help/readme/frontmatter/export checks, and new check-kb-brain unit tests covering init, workspace lifecycle, routing/IDs, seal/amend, and brief candidate-spec generation)

cursoragent and others added 2 commits August 4, 2026 10:41
Add repository-native KB-Brain memory (workspaces, routing, seal/amend)
and brief-to-milestone candidate-spec expansion. Existing PAAD skills are
unchanged; both capabilities are invoked explicitly. Includes stdlib
kb_brain.py tooling, templates, tests, docs, and regenerated exports.

Co-authored-by: Kenny Webb <KennySmash@users.noreply.github.com>
…6222

feat: add KB-Brain memory and brief rumination skills
@KennySmash

Copy link
Copy Markdown
Author

Hi Ovid, this is an ai assisted distillation of some battle tested techniques that I've been using over the past year in my personal projects to help combat tech debt and manage shippable milestones and thought it would be a great fit to implement something similar here, I've marked the PR as draft as its more of an idea rather than just a straight merge as I don't want to step on toes architecturally

@Ovid

Ovid commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Hi @KennySmash. Sorry I didn't see this sooner. I'm on holiday for a couple of weeks, but I'll try to squeeze in investigation of this.

Without digging in, my first suggestion is to fix what is probably one of my worst failures: skill names. I get them wrong all the time. For this, I would want new skill names. Many of the development teams I train are comfortable in English, but not native speakers. Thus, "kb-brain" and "brief-ruminate" are names that I can grok, but are likely to be confusing and harder for non-native English speakers to understand and/or remember.

@KennySmash

Copy link
Copy Markdown
Author

Completely fair point, I'll confer with some multi-national dev friends and get some idea's and update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants