Explore skills
Showing 30301–30330 of 77104 skills
Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine implementation contracts (APIs and data models) that developers will build against during PRD v0.6 Architecture. Triggers on requests to define APIs, design database schema, create data models, or when user asks "define APIs", "data model", "database schema", "API contracts", "technical spec", "endpoint design", "schema design". Consumes ARC- (architecture), TECH- (Build items), UJ- (flows), SCR- (screens). Outputs API- entries for endpoints and DBT- entries for data models. Feeds v0.7 Build Execution.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexTransform v0.6 specifications into context-window-sized work packages (EPICs) during PRD v0.7 Build Execution. Triggers on requests to create epics, scope work, break down implementation, or when user asks "create epics", "scope work", "break down work", "context window sizing", "what to build first?", "implementation planning", "epic breakdown". Consumes API-, DBT-, FEA-, ARC-. Outputs EPIC- entries with objectives, ID references, dependencies, and context windows. Feeds v0.7 Test Planning.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexExecute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases", "test coverage", "TEST-", "test-first". Consumes EPIC- (scope), API-, DBT-, BR-, UJ-. Outputs TEST- entries with Given-When-Then format. Feeds v0.7 Implementation Loop.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDesign the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Triggers on requests to set up a changelog system, publish releases, or when user asks "how should we publish releases?", "changelog as marketing", "release notes", "Stripe-style changelog", "what to do with our release notes", "ship and tell". Outputs MON-CHG-* changelog entries and per-channel formats.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexEstablish baseline → snapshot → compare → history monitoring for any KPI, config, or metric that can drift during PRD v0.8 Deployment & Ops. Triggers on requests to monitor drift, baseline a value for later comparison, or when user asks "how do we track if X changes?", "baseline this", "config drift", "performance regression", "metric drift", "compare to last week", "is this getting worse?". Outputs MON-DRIFT-* entries with baseline + comparison rules.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine lifecycle stages and marketing → sales / CSM handoff rules for leads captured by GTM channels during PRD v0.8 Deployment & Ops. Triggers on requests to set up lead lifecycle, define MQL/SQL criteria, build handoff process, or when user asks "what's an MQL?", "marketing to sales handoff", "lead lifecycle", "lead routing", "RevOps", "MOPS", "marketing operations". Outputs BR-MOPS-* lifecycle rules and GTM-MOPS-* handoff flow entries.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON- entries with monitoring rules and alert configurations.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine release criteria, deployment environments, and rollback strategies during PRD v0.8 Deployment & Ops. Triggers on requests to plan releases, define deployment criteria, or when user asks "how do we deploy?", "release criteria", "deployment plan", "rollback strategy", "go-live checklist". Outputs DEP- entries with deployment steps and release criteria.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexCreate operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Triggers on requests to create runbooks, document procedures, or when user asks "how do we handle incidents?", "runbook", "operational procedures", "on-call guide", "incident response", "maintenance procedures". Outputs RUN- entries with step-by-step operational procedures.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexAudit how AI search engines (ChatGPT, Perplexity, Google AI Overviews, Claude) describe and recommend your product, then propose fixes. Triggers on requests to audit AI search visibility, improve AEO/GEO, check ChatGPT/Perplexity coverage, or when user asks "do we show up in AI search?", "AEO audit", "generative engine optimization", "AI discoverability", "how does ChatGPT describe us?", "Perplexity ranking". Outputs GTM-AEO-* entries and a Coverage Matrix.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexGenerate "X vs Y" and "Alternative to X" SEO/CRO pages targeting competitive search intent during PRD v0.9 Go-to-Market. Triggers on requests to build comparison pages, target competitive search traffic, or when user asks "build alternatives pages", "X vs Y page", "competitor comparison page", "we're better than X page", "capture branded search", "competitive SEO". Outputs SCR-ALT-* page specs and GTM-* channel entries.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexBuild Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market. Triggers on requests to plan cold outreach, founder-led sales, or when user asks "cold email sequence", "outbound campaign", "founder outreach", "LinkedIn outreach", "Tier 1 personalization", "predictable revenue", "sales cadence", "BDR sequence". Outputs GTM-OUT-* sequence entries and lead-list references.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexEstablish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS", "voice of customer". Outputs CFD- entries specialized for post-launch feedback capture.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexOrchestrate go-to-market strategy by running positioning, offer construction, and channel allocation as a sequenced workflow during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "GTM", "launch this product". Chains three framework-grounded sub-skills (Dunford → Hormozi → ORB) and reconciles their outputs.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexBuild a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market. Triggers on requests to plan HN/Reddit launch, "Show HN" post, community launch, or when user asks "HN launch", "Show HN", "Reddit launch", "launch on /r/SaaS", "Product Hunt vs HN", "community launch", "developer launch". Outputs GTM-* with Type=Channel-HN / Type=Channel-Reddit entries with timing, title, story angle, and engagement plan.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexAllocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Triggers on requests to pick launch channels, distribute the offer, build a channel portfolio, or when user asks "where do we launch?", "what channels?", "ORB", "owned vs rented vs borrowed", "channel allocation", "channel mix", "Corey Haines launch". Outputs GTM-* entries with Type=Channel, a channel-mix matrix, and a launch sequence.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexConstruct a high-conversion offer using Alex Hormozi's value equation and Grand Slam Offer mechanics during PRD v0.9 Go-to-Market. Triggers on requests to design the offer, set up the pitch, build bonuses or guarantees, or when user asks "how do we package this?", "what's the offer?", "build a grand slam offer", "Hormozi", "$100M offers", "guarantee", "bonus stack". Outputs GTM-* entries with Type=Offer / Type=Guarantee and BR-PRICING-* updates.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDefine product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning", "obviously awesome", "market frame of reference", "positioning statement". Outputs GTM-* entries with Type=Positioning and BR-POS-* positioning rules.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexBuild customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE-* evidence entries, GTM-CASE-* marketing assets, and updates ADO-REF-* with story status.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexEstablish weekly customer-discovery cadence and Opportunity Solution Tree practice using Teresa Torres's Continuous Discovery Habits framework during PRD v1.0 Market Adoption. Triggers on requests to set up discovery cadence, build opportunity solution tree, run weekly customer interviews, or when user asks "Torres", "continuous discovery", "opportunity solution tree", "outcomes vs outputs", "weekly interviews", "assumption mapping". Outputs CFD-* discovery entries and updates to ADO-STAGE-* and PER-* with new evidence.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexApply Rob Fitzpatrick's Mom Test discipline to customer interviews during PRD v1.0 Market Adoption. Triggers on requests to interview customers, run discovery calls, validate ideas with users, or when user asks "how do I interview customers?", "Mom Test", "Rob Fitzpatrick", "customer interview", "user research without lies", "talking to humans", "discovery conversation". Outputs CFD-* discovery entries with Mom Test-calibrated confidence.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexSystematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Triggers on requests to collect testimonials, set up social proof harvest, gather customer quotes, or when user asks "how do we get testimonials?", "social proof harvest", "NPS responses", "testimonial wall", "customer quotes", "post-purchase survey", "milestone follow-up". Outputs CFD-TST-* testimonial entries and GTM-TST-* placement assets.
mattgierhart/PRD-driven-context-engineering
Stars: 179Claude CodeCodexDiscover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
rse/ase
Stars: 77Claude CodeCodexImplement current or given task plan, optionally as an implementation draft attachment only. Use when the user calls to "implement", "realize", "draft", "dry-run", or "test-drive" the "task", "plan", "spec", or "specification".
rse/ase
Stars: 77Claude CodeCodexIntegrate the change set or implementation draft of the current or given task plan into its target. Use when the user calls to "deliver" or "apply" the change set or draft of the "task" or "plan". For merging a plain Git branch, use `ase-repo-merge` instead.
rse/ase
Stars: 77Claude CodeCodexCheck the branch marks its generated files, review it with /code-review at high, then answer the findings with /code-review-response.
wado-lang/wado
Stars: 120Claude CodeCodex