Core Stack

The core stack is the part of Uncle Bob that applies before language or framework specialists matter. It gives the agent an operating model for quality, planning, authoring, and governance.

The Four Core Skills

• ub-quality keeps work readable, scoped, and reviewable.
• ub-authoring keeps reusable skill guidance portable and routeable.
• ub-workflow chooses the right planning surface and carries larger work through durable artifacts.
• ub-governance defines when evidence, gates, exceptions, and decision records are needed.

Why This Matters

For developers, the core stack reduces hidden decisions. The agent has a shared model for when to ask, when to plan, when to execute, and when to validate.

For managers, the core stack makes agent work easier to govern. Planning depth, evidence needs, and escalation points are visible instead of implied.

Pros And Cons

Pros:

• repeatable operating model across projects
• fewer ad hoc decisions hidden in chat
• clearer handoffs after long or interrupted work

Cons:

• more repo surfaces to keep synchronized
• heavier than a one-off prompt for tiny experiments
• skill authors must preserve portability boundaries

Use The Core Stack When

• the task needs planning before implementation
• review quality matters more than raw speed
• an agent should explain tradeoffs before choosing a path
• work may need to stop, resume, or transfer to another operator
• risk or evidence expectations are unclear