pythia-packagelisted
Install: claude install-skill thaildhe172591/pythia
# Designing Packages, Procedures, Functions, Triggers
**Announce at start:** "Using pythia-package — designing the spec before the body."
**Phase:** Learn → Ask → Do — neighbours and callers first, the contract agreed, then spec and body as two files
`pythia-write` makes new code indistinguishable from the codebase. This
skill adds what the codebase may not show: how a unit should be *shaped*
so that callers can trust it. When the house does it differently, the house
wins — `.pythia/conventions.md` first, `reference/plsql-standards.md` for
everything it does not decide.
## The Iron Law
```
THE SPEC IS A CONTRACT: DESIGN IT FIRST, AND NEVER BREAK IT SILENTLY
```
A package spec change invalidates every dependent at once; a body change
invalidates nothing. That asymmetry decides most of the design.
## The Workflow
1. **Learn** — `pythia similar <NAME>` and `pythia src` on the top two or
three; `pythia args` for every unit you will call; `pythia impact <PKG>`
when the package exists (a spec change reaches all of it); `pythia cols`
for every table touched.
2. **Shape the contract** (open behaviour goes to `pythia-spec` first):
- **Package, not standalone**, unless the house writes standalone units:
encapsulation, private helpers, and body changes that invalidate nobody.
- **Public surface = what callers need.** Everything else private, in
the body only. New public items go at the **end** of the spec — with
fine-grained dependency tracking (11g