Enforce contract-first architectural design with explicit assumption tracking and stress testing.
npx skills add https://github.com/susamn/skills --skill brainstorming-susamn
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/susamn/skills/tree/main/brainstorming Command: npx skills add https://github.com/susamn/skills --skill brainstorming-susamn
This Skill eliminates the risk of costly late-stage architectural rewrites caused by ad-hoc, assumption-heavy planning that overlooks critical data contracts, undefined trust boundaries, and unhandled failure states. It enforces a rigorous, principal-aware, contract-first workflow to surface hidden design flaws before implementation begins.
Use the brainstorming skill to run a full architectural brainstorming session for your new distributed payment processing system, starting with the reframe check to validate your core problem statement.
High-intent search queries and answers about installing and using this skill.
Distributed system design with explicit data contracts requires a contract-first workflow that maps trust boundaries for all principals and documents hard constraints before selecting architectural paradigms. This surfaces hidden design flaws and unhandled failure states before implementation begins.
Contract-first design is an architectural planning approach requiring explicit data contract definition at every system boundary before considering paradigms. You need it when planning distributed, stateful, or cross-boundary systems to prevent costly late-stage rewrites caused by unstated assumptions.
Brainstorming architectural designs for cross-boundary systems requires a spiral iterative workflow with reframe checks, boundary definition, paradigm divergence, and stress testing. This process surfaces undefined data contracts and unhandled failure states while allowing re-entry to earlier steps when constraints emerge.
Yes, contract-first design applies to stateful distributed systems by enforcing explicit assumption tracking and multi-paradigm divergence. It validates latency constraints against stateful paradigms and produces verifiable, production-ready system blueprints for cross-boundary architectures.
Eliminating hidden assumption flaws in technical roadmap development requires rigorous stress testing and assumption mapping across trust boundaries. A principal-aware workflow validates core problem statements through reframe checks before committing to specific architectural paradigms.
Architectural designs fail in production because ad-hoc planning overlooks critical data contracts between services, leaving trust boundaries undefined and failure states unhandled. Contract-first enforcement requires documenting these constraints upfront to avoid sunk-cost fallacies during implementation.
TestAny-ioCreates structured, ready-to-review PRD drafts from stakeholder input and context.
KaranKathur06Transforms feature requests into full-stack implementation blueprints with risk and deployment planning.
heaptracetechnologyAutomate API contract testing with schema validation and OpenAPI checks.
lidessenDesign system architectures from primitives for AI-native paradigms.
