Callstack Diff Logic-Flow Implementation Notes

Updated: 2026-08-08 23:08 CDT

Design decisions

• Decision: Treat the grievance-routing pipeline only as a concrete branching-flow example.
  Why: The handoff explicitly excludes implementing the endpoint or its integrations.
• Decision: Inspect the current CLI, skill guidance, and history before changing behavior.
  Why: The reported miss may be discoverability or prior-agent misuse rather than an unsupported input model.
• Decision: Classify the miss as a skill discoverability and guidance defect, not a renderer defect.
  Why: The existing CLI rendered the branching grievance flow correctly once represented as a minimal temporary TypeScript model, but the package skill was neither globally deployed nor described for prose architecture flows.
• Decision: Keep one canonical skill at skills/catalog/callstack-diff/SKILL.md and link the package development path to it.
  Why: Global catalog placement makes the skill discoverable while the package CLI can continue bundling the same content without a duplicate source.

Deviations from spec

• None.

Tradeoffs considered

• Options: Add a prose-flow renderer, change only the package-local skill, or deploy one canonical skill with a temporary-model workflow.
  Chosen: Deploy one canonical skill and retain the existing renderer.
  Reason: The real CLI already preserves the shared prefix and distinct branches; only discovery and guidance were missing.

Open questions

• None.