Loading...
Loading...
Found 4 Skills
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.
Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
This skill helps create RFC (Request for Comments) documents for proposing new features, architectural changes, or significant enhancements to the project. It provides templates, structure guidelines, and best practices for writing effective technical proposals. Use this skill when planning major changes that need team review and discussion. IMPORTANT: Before writing any RFC, you MUST conduct online research to survey current industry best practices, mainstream implementations, and latest trends.
Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.