glennandClaude Opus 5
8ea297e8bf
Callista consumes this pipeline for both plain Odoo implementations and vertical demos, and is not a maintainer upstream — so the generic demo craft that had accumulated in the buildease-demo vertical skill lands here instead, where every engagement can reach it. Moved in from buildease-demo (they were never construction-specific): - Phase A: discovery brief from a transcript, notes, email, Knowcap, or a batched interview. Replaces the Knowcap-bound step 1. Infers before it asks. - Fork the slow half: instance prep and client research as two parallel subagents, then join. - Purge test residue: ordering, traps, read-back-the-counts evidence. - Phase C: objection sheet, scoped quote, implementation timeline, SOW. New here: - Extension points — a vertical supplies module routing, solution precedence, purge chain, demo-data policy and follow-through framing, and nothing else. Anything it needs beyond those is a gap to fix here, not to work around. - Named steps instead of numbered ones. Numbering meant an upstream renumber silently misrouted an extending skill with nothing to detect it. Renamed the skill to callista-odoo-demo: skills resolve by directory name, so a same-named fork shadows upstream depending on install order, and two people would build different demos from the same brief. MIT retained; SMEtools copyright kept, Callista added for modifications. Fork point and divergence recorded in UPSTREAM.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.3 KiB
Upstream
Fork of Smetools/odoo-demo-architect (MIT).
| Fork point | ada2751 — docs: credit Claude Code (agent) + Knowcap (memory via MCP) throughout |
| Forked on | 2026-07-31 |
| Upstream state at fork | 2 commits, no tags, no releases |
Callista is not a maintainer upstream, so changes land here rather than as PRs. Upstream is effectively inert; pull from it deliberately rather than tracking it.
git remote add upstream https://github.com/Smetools/odoo-demo-architect
git fetch upstream && git log --oneline HEAD..upstream/main
Why the fork exists
Callista runs this pipeline for both plain Odoo implementations and vertical demos
(BuildEase/construction via the buildease-demo skill). Three things it needed are not
upstream's problem to solve:
| Divergence | Upstream | Here |
|---|---|---|
| Discovery source | Step 1 pulls the transcript from Knowcap over MCP; everything else is a fallback mentioned in passing | Phase A takes a transcript, notes, an email thread, Knowcap, or a batched interview, and infers before it asks. Knowcap is one source among several |
| Build parallelism | Linear steps 3–7 | Fork the slow half — instance prep and client research run as two parallel subagents, then join |
| After the demo | Ends at hand-off | Phase C — objection sheet, scoped quote, implementation timeline, SOW |
| Extensibility | None; a vertical would fork the whole pipeline | Extension points — a vertical supplies routing, precedence, purge chain, demo-data policy, and nothing else |
| Step references | Numbered ### 1.–### 9. |
Named steps. Numbers meant a renumbering upstream silently misrouted an extending skill |
| Purge | One line inside step 7 ("delete the throwaway") | Purge test residue — ordering, traps, and read-back-the-counts evidence |
Renamed
The skill is callista-odoo-demo, not odoo-demo-architect. Skills resolve by
directory name under ~/.claude/skills/, so a same-named fork would silently shadow
upstream depending on install order — and two people would build measurably different
demos from the same brief. Keep the names distinct.
Attribution
MIT. LICENSE retains the SMEtools copyright as required and adds Callista's for the
changes. Keep both.