Discipline

What counts as skipping:

• Omitting a step entirely
• Replacing a step with a shortcut
• Producing placeholders/stubs instead of completing work
• Adding nolint, skip, pending markers to bypass work

KB Curator Integration

MANDATORY triggers (no exceptions)

Three situations ALWAYS require delegating to KB Curator before your task is considered complete:

1. Project or feature work — When a feature, task set, or project milestone is completed. Document what was built, changed, or decided.
2. Exploration or investigation findings — When research, codebase exploration, or investigation produces new understanding. Document discoveries, patterns found, and conclusions reached.
3. Agentic flow or config changes — Any modification to agent files, skill files, command files, AGENTS.md, opencode.json, or any OpenCode configuration. Delegate immediately after the change is verified.

Run KB Curator as a fire-and-forget background task so it does not block your work:

task(
  subagent_type="Knowledge Base Curator",
  run_in_background=true,
  load_skills=[],
  prompt="[describe what changed and what needs documenting]"
)

Contextual triggers (use judgement)

For other work, invoke KB Curator when there is lasting documentation value:

• New features or plugins → Document in the relevant KB section
• Architecture decisions → Record in the KB under AI Development System
• Bug fixes with broader implications → Note in KB if it affects documented behaviour

Skip KB Curator for: routine task execution, minor code fixes, refactors with no new behaviour.

Worktree Safety (MANDATORY)

Agents may work in git worktrees outside the main working directory. Two branches are protected:

• main — Production branch. NEVER modify unless the user explicitly grants permission.
• next — Integration branch. NEVER modify unless the user explicitly grants permission.

Before operating in any worktree:

1. Verify which worktree/branch you are in
2. Confirm it is NOT a protected branch — or that the user explicitly authorised it

Modifying a protected worktree without explicit permission is a blocking violation.

Anti-patterns to avoid

• Skipping steps because they "seem unnecessary"
• Self-authorising shortcuts without orchestrator approval
• Producing stubs or placeholders instead of real work
• Modifying main or next worktrees without explicit user permission
• Forgetting KB Curator after setup changes or project completion
• Running KB Curator synchronously when it should be fire-and-forget

KB Reference

~/vaults/baphled/3. Resources/Knowledge Base/AI Development System/Skills/Core-Universal/Discipline.md

Related skills

• pre-action — Decision framework that runs before execution; discipline ensures execution completes fully
• memory-keeper — Captures discoveries; discipline ensures KB Curator documents them
• clean-code — Code quality principles; discipline ensures they are applied without shortcuts