smyrick/smyrick-skills
Shane Myrick's reusable workflows for research, planning, code review, and writing.
Explain a codebase’s architecture from repository evidence, with optional documentation and self-contained HTML diagrams.
Guide Shane through a PR or local diff with a compact brief on defects, architecture, and consequential technical and product choices.
Organize planned or ongoing code changes and long coding conversations into reviewable chunks, self-contained handoffs, and concise PR documentation.
Remove generic AI-writing patterns from prose while preserving facts, meaning, and the writer’s voice.
Create and maintain scoped PRODUCT_TERMS.md glossaries defining product terms, domain rules, and relevant code references.
Run mock interviews tailored to available candidate, role, and interview-stage information, with evidence-based feedback and optional notes.
Research a non-code decision, recommend an option, and outline concrete next steps. Select direct research, focused read-only leaf scouts, or an internal durable research subworkflow based on the evidence needed.
Research a proposed code change and resolve the decisions needed for an implementation plan. Select direct inspection, focused read-only leaf scouts, or an internal durable research subworkflow without modifying code.
Coordinate research with authorized persistence and return a reusable evidence handoff. Use when planning or decision work needs multiple focused passes, persistent findings, recovery, or a reusable evidence handoff.
Make the current response concise and direct while preserving technical depth, caveats, and required safety communication.
Turn a product problem into a requirements document with explicit scope, product decisions, and testable acceptance criteria.