tomwangowa
@tomwangowa
Public Skills
qa-to-notes
by tomwangowa
Save Claude Code Q&A conversations as structured Obsidian-compatible knowledge notes, or rewrite fact-checks into corporate-friendly Teams publish format. Use when user wants to persist conversation content as a markdown file, or rewrite analysis for team sharing.
brainstorming
by tomwangowa
Use before any creative or implementation work — new features, architecture changes, refactoring, or workflow design. Explores intent through Socratic dialogue, proposes approaches with trade-offs, and produces an approved design before any code is written.
role-orchestrator
by tomwangowa
Orchestrates a multi-role development pipeline (PM → RD) using subagent dispatch. Reads project-profile.yaml to calibrate role behavior by project size. Each role runs in an isolated subagent to prevent context pollution. Includes gate checks for user approval between phases. Triggered by "role orchestrator", "multi-role pipeline", "PM then RD", "start role pipeline", or "orchestrate roles".
role-rd
by tomwangowa
RD (Developer) role for the multi-agent role system. Produces structured design artifacts calibrated by project size (small/medium/large), taking PM requirements as input. Invoked by role-orchestrator via subagent dispatch, or directly for standalone design work. Triggered by "RD analysis", "technical design", "role-rd", or when role-orchestrator dispatches the RD phase.
role-pm
by tomwangowa
PM (Product Manager) role for the multi-agent role system. Produces structured requirements artifacts calibrated by project size (small/medium/large). Invoked by role-orchestrator via subagent dispatch, or directly for standalone requirements work. Triggered by "PM analysis", "requirements gathering", "role-pm", or when role-orchestrator dispatches the PM phase.
ai-weekly-insight
by tomwangowa
Produce weekly AI news deep-analysis reports for TrendLife AI Taskforce. Use when asked for "AI 週報", "weekly insight", or weekly AI news analysis.
micro-poc-validator
by tomwangowa
Empirically validate technical assumptions through minimal code experiments (5-30 min spikes). Use when a tech-feasibility assessment or design document contains claims that can be proven or disproven by running actual code. Triggered by "validate this assumption", "can X actually do Y?", "prove it with code", or "micro-poc".
tech-feasibility
by tomwangowa
Use when evaluating whether a specific technology, tool, or approach can solve a given problem before committing to implementation. Triggered by questions like "can X do Y?", "will X work for Y?", "is X feasible for Y?", or "should I use X to achieve Y?"
tech-research-pipeline
by tomwangowa
Orchestrates a full technical research workflow by chaining specialized skills in sequence: brainstorming → tech-feasibility → assumption-extractor → micro-poc-validator → critical-research → narrative-auditor → research-cross-validator → research-synthesis. Use when evaluating a technology choice, planning a migration, or making any significant technical decision that warrants rigorous multi-angle analysis. Triggered by "full research pipeline", "rigorous tech evaluation", "research pipeline", or "evaluate [tech] thoroughly".
narrative-auditor
by tomwangowa
Audit external narratives (articles, posts, marketing copy) against primary sources, or speak on behalf of the user as their AI proxy. Use when asked to "fact-check", "verify this article", "audit this claim", "help me respond", "speak for me", or "supplement context".
assumption-extractor
by tomwangowa
Systematically extract explicit and implicit assumptions from technical documents, design plans, or feasibility assessments. Classifies each assumption by visibility (explicit/implicit), verification status (verified/unverified/falsified), recommended verification method, and risk impact. Use when reviewing any technical plan before committing to implementation, or when a tech-feasibility report needs assumption auditing.
research-cross-validator
by tomwangowa
Cross-validate technical claims using multiple independent verification strategies (official docs, counter-examples, source code inspection). Use when a tech-feasibility report, design document, or any technical analysis contains claims that were verified by only one method or one AI session. Triggered by "cross-validate", "verify these claims", "double-check this", or "independent verification".
codebase-audit
by tomwangowa
Claims-first codebase audit that extracts documentation claims and verifies them against code. Use when asked to "audit", "verify docs match code", "check if README claims are true", or "validate documentation accuracy". Falsification-first approach.
research-synthesis
by tomwangowa
Use after running 2+ research skills (critical-research, tech-feasibility, narrative-auditor, codebase-audit) to synthesize findings into a unified decision document. Resolves conflicts between sources, weighs evidence, and produces an actionable recommendation.
critical-research
by tomwangowa
Falsification-first research skill that actively seeks counter-evidence before supporting evidence to eliminate cognitive biases and ensure rigorous, objective conclusions.
work-log-analyzer
by tomwangowa
Analyze work logs and journals to answer questions about project history, decisions, TODOs, and timeline evolution. Use this Skill when the user wants to query their work journal, track task progress, or understand how decisions evolved over time.
presentation-planner
by tomwangowa
Use before creating presentations — transforms a topic or rough outline into a complete Slide Plan with narrative strategy, audience analysis, and per-slide detail. Auto-chains to interactive-presentation-generator for production.
report-generator
by tomwangowa
Use when generating status reports, project summaries, retrospectives, or any structured report from work logs, git history, and activity records. Supports weekly, monthly, project, sprint, incident, and retrospective report types.
code-review-claude
by tomwangowa
Perform native code review (< 30 seconds) using Claude Code's built-in capabilities without external dependencies. Use for rapid validation checks during development. Triggered by 'quick review', 'native review', or 'fast code check'.
code-review-gemini
by tomwangowa
Perform deep, thorough code review using Gemini AI. Use this Skill when user explicitly requests 'gemini review', 'thorough review', 'detailed review', or 'deep review'. Default reviewer for code reviews per CLAUDE.md preferences.
verification-before-completion
by tomwangowa
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
pr-review-assistant
by tomwangowa
Assist in reviewing pull requests by analyzing diffs and providing structured feedback. Use this Skill when the user asks to review a PR, analyze pull request changes, check code quality in PRs, or help with code review.
skill-auditor
by tomwangowa
Audit Claude Code skills for quality, security, and best practices. Use when reviewing SKILL.md files, ensuring skill quality standards, or before sharing skills with team.
ui-design-analyzer
by tomwangowa
Analyze UI/UX design from screenshots. Use this Skill when the user asks to analyze UI design, review interface screenshots, check design quality, evaluate user experience, or get design improvement suggestions.
code-story-teller
by tomwangowa
Analyze git history to tell the story of how code evolved. Use this Skill when the user asks to understand code history, explain evolution, show file timeline, or understand design decisions behind code.
activity-logger
by tomwangowa
Records work activities from the current session for cross-session aggregation and work log generation
interactive-presentation-generator
by tomwangowa
Generate interactive presentation from an outline or brief. Creates markdown-based presentations (Marp/Slidev/reveal.js) or standalone HTML presentations. Use when user asks to create slides, make a presentation, or generate a deck from an outline.