← all publishers

jessedegans

@jessedegans source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Adr · jessedegans

   Record Architecture Decision Records (ADRs) when significant technical decisions are made. MUST trigger when switching, migrating, or replacing libraries, SDKs, frameworks, databases, or infrastructure. MUST trigger when making decisions that shape how the system works going forward: deployment strategies, service boundaries, data flow patterns, auth models, API design. Also trigger when choosing between alternatives, making trade-offs, or changing a previous approach. Common signals: "let's go with X", "we should use Y", "I've decided to", "switching from X to Y", "the trade-off is", "pros and cons of", "why did we choose X?", or "document this decision". Even if the user doesn't say "ADR", if a decision is being made that future-them would want to remember the reasoning for, this skill applies. Record the ADR proactively, don't wait to be asked.
   0
   installs
2. ▌
   Ship · jessedegans

   Use when shipping, deploying, creating a PR, or preparing a release. Review staleness detection, gated review requirement with override options, and a structured release flow. Use when: user says "ship it", "create a PR", "let's deploy", "ready to merge", or is preparing code for release.
   0
   installs
3. ▌
   Debug · jessedegans

   Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Enforces root cause investigation before fixing. No guessing, no shotgun debugging. Hard stop after 3 failed hypotheses. Use when: tests fail, errors appear, behavior doesn't match expectations, or something "just broke."
   0
   installs
4. ▌
   Research · jessedegans

   Use when the user asks a research question, wants to explore a topic, compare options, or needs to investigate something before making a decision. Sets up a structured research folder with living documents and uses sub-agents for parallel exploration. Use when: user says "research X", "look into Y", "compare A vs B", "what are our options for", "investigate", "explore", or asks a question that needs multiple sources to answer well.
   0
   installs
5. ▌
   Security · jessedegans

   Use when reviewing code for security vulnerabilities, before shipping to production, or when the user asks for a security audit. Runs OWASP Top 10 + STRIDE analysis with a strict false positive filter. Confidence gate at 8/10. No theoretical hand-waving.
   0
   installs
6. ▌
   Preflight · jessedegans

   Use before claiming work is done, before committing, before creating PRs, or before saying "it should work now." Enforces running verification commands and reading their output before making any completion claims. Evidence before assertions.
   0
   installs
7. ▌
   Brainstorm · jessedegans

   Use before starting any feature, entering unfamiliar code, or beginning a non-trivial task. Enforces understanding before action. No code, no scaffolding, no implementation until the problem is explored and a direction is approved. Use when: user says "let's build X", "add feature Y", "I want to create Z", or begins work on something that needs design thinking.
   0
   installs