What problem does it solve? Turning scattered PRDs, tickets, URLs, notes, and codebase evidence into a coherent, implementation-ready technical design is time-consuming and often requires senior engineering judgment. This Skill synthesizes heterogeneous inputs, analyzes the current repository, compares architecture options, and publishes a decision-ready technical design document directly to Notion. ## Core Features & Use Cases - Resource Synthesis: Fetches and normalizes PRDs, Jira/Confluence pages, URLs, local files, transcripts, and raw notes into a source ledger with confidence labels. - Codebase-Grounded Design: Inspects the current repository for architecture, data models, APIs, jobs, infrastructure, and tests before recommending an approach. - RFC/ADR-Style Decisions: Compares credible implementation options, records decision rationale, rejected alternatives, and revisit triggers. - Enterprise Dependency & IaC Planning: Evaluates cloud-native services versus vendor wrappers and includes Terraform/IaC plans when infrastructure changes are needed. - Use Case: Given a PRD link, a Confluence page, and access to the repo, the Skill produces a Notion technical design with requirements tables, options comparison, rollout plan, and risks—ready for Jira planning. ## Quick Start Use the resources-to-notion-technical-design skill to analyze my PRD and this repository, then publish a technical design document to my Notion page.
