crissmoldovan
- 20 skills
- 0 followers
- 7 hours ago last updated
- ▌
- ▌ Blast Area · crissmoldovan bundleMap what a set of changes would affect before making it: callers, data contracts, jobs, UI, tests, build toolchains, deploy ordering, and second-order readers — with searched negatives and a list of what the map cannot see. Use when you need to know what a change would break.
- ▌ Delphi Ground · crissmoldovan bundleBuild a verified-facts briefing before asking anyone — human or agent — to reason about an artefact, and refuse to certify one when too little can be checked. Use when a review, a fan-out or a persona exercise would otherwise run on invention.
- ▌
- ▌ Delphi Imagine · crissmoldovan bundleReview an artefact from a named perspective without inventing the world it lives in: grounded scenarios, a mandatory case where the thing is useless, and every request traced to a moment and costed. Use when you want a critique that can be checked rather than one that reads well.
- ▌ Release Ledger · crissmoldovan bundleOnboard a since-you-have-been-gone release ledger into any product: capture merged work, analyse and categorise it, and show each user what changed since they last looked.
- ▌
- ▌ Github Webhooks · crissmoldovan bundleAdopt and manage GitHub webhook handling in an app: endpoint setup, signature verification, event routing, and a working reference for every event type you route.
- ▌ Decision Journal · crissmoldovan bundleRecord why a decision was made, anchored to evidence a reader can check, so months later the question 'why is this like this, and what did we already rule out' has an answer. Use when work is worth being able to reconstruct.
- ▌ Describe Changes · crissmoldovan bundleDocument what a change actually did: analyse a commit, PR, or merge, classify it, and write short, medium, and detailed descriptions anchored to the diff.
- ▌ New UX Discovery · crissmoldovan bundleDiscover UX improvements a codebase can already support — across UI, API, CLI, MCP and notifications — and gate every candidate through a not-already-implemented sweep and a no-confusion check before proposing it. Use when you want evidence-backed UX opportunities, riding a change or from pure analysis.
- ▌ Land Complex Change · crissmoldovan bundleLand a complex change with reduced side effects and regressions: declare a touch-set budget from its blast map, arm a regression gate per affected surface, and stop when work strays outside the budget. Use when a change is too risky to build without contained side effects.
- ▌
- ▌
- ▌ Investigate Codebase · crissmoldovan bundleAnswer a question about a codebase with evidence that can prove it — score complexity before spending, fan out searches with controls, reconcile contradictions, and say what was not searched. Use when a code question needs a defensible answer, not a guess.
- ▌ Visualise Blast Area · crissmoldovan bundleRender a change's blast map as diagrams — mermaid first, optionally one self-contained interactive HTML — with changed-vs-affected styling and blind spots stated on the diagram itself. Use when a blast-area map needs to be seen, shared, or dug into.
- ▌
- ▌ Resolve Problem Report · crissmoldovan bundleResolve a problem report end to end: reproduce the claim, dig to root cause or implications, offer candidate fixes with trade-offs, spec the chosen one, and land it through gated review. Use when a bug or feature report needs investigating and resolving rather than a quick patch.
- ▌ Derive Codebase Context · crissmoldovan bundleDerive agent context, enforced boundaries, and an operational atlas from the repo itself. Use when agents keep losing the shape of a large codebase.
- ▌ Secure Credential Setup · crissmoldovan bundlePlace and verify secrets without exposing their values.