Use when implementation work starts on a feature or bug fix: writing or modifying source code, adding tests, or closing out a branch. Covers TDD-first, scope integrity, secret and security hygiene, dual post-implementation review (code reviewer plus spec reviewer), and finish-branch closure. Triggers on "implement"…
Use when the user wants the plan rendered as an interactive HTML report or exported to PDF/DOCX/PPTX. Triggers on 'HTML report', 'export to PDF', 'export document', 'downloadable report', 'PDF/DOCX/PPTX', and the same intent in any language.
Use when the user needs an engineer-ready PRD or a development handoff package (CLAUDE.md, TASKS, TICKETS, ARCHITECTURE, setup). Triggers on 'PRD', 'product requirements doc', 'handoff to engineering', 'dev handoff', 'TASKS.md', 'TICKETS', 'architecture doc', and the same intent in any language.
Use before any major initiative, architecture decision, or competitive strategy choice. Triggers on "should we build this?", "how do we compete?", "is the timing right?", or when evaluating resource allocation. Scores five parallel factors (Tao/Heaven/Earth/Command/Method) → go/caution/stop verdict.
Modern Go (Golang) development best practices (2024-2025). Use for project setup, modules, generics, concurrency, testing, HTTP/gRPC services, databases, CLI, linting, Docker, and production deployment.
Modern Python development best practices (2024-2025). Use this skill for project setup, dependency management, typing, testing, linting, async patterns, FastAPI, SQLAlchemy, Pydantic, and production deployment.
Surfaces the assumptions a product or strategy depends on, classifies them by criticality and evidence quality, and produces a prioritized test plan. Use when: assumption mapping, identify assumptions, what could go wrong, leap-of-faith assumptions, riskiest assumption test, RAT, assumption inventory, validate before…
Structured competitive teardown for product discovery - surface the 4-6 dimensions buyers actually weigh, score every competitor on each, and identify exploitable gaps. Use when: competitive analysis, competitor teardown, market positioning, where do we win, where do we lose, competitive gap analysis, competitor audit.
Turn raw research into Jobs-to-be-Done statements showing what users are really trying to accomplish. Use when: extract jobs, jtbd analysis, jobs to be done, what job is the user hiring, underlying user needs.