Loading…
Not enough history yet: 3 of 7 days recorded. Until then this list is ordered by the most recent content change.
77104 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| blast-radiusykorovko/dotagentsReview what a code change could break beyond the diff and prove the main fact that makes it safe. Use only when the user explicitly asks for a blast-radius review, asks what a change could break, or requests extra scrutiny of a suspicious diff. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| handoffykorovko/dotagentsCreate a concise handoff document so a fresh agent or new session can continue the current work. Use only when the user explicitly asks for a handoff, continuation brief, or context transfer. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| howykorovko/dotagentsExplain how code, a subsystem, or an architectural flow works. Use only when the user explicitly asks for a code walkthrough, runtime trace, ownership or layering explanation, or architecture critique. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| show-me-your-workykorovko/dotagentsKeep a reviewable TSV decision trail for long-running or unattended work. Use only when the user explicitly asks for show-me-your-work or a decision log. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| unslopykorovko/dotagentsEdit prose to remove common AI-generated patterns and add a natural voice. Use when the user asks to revise, polish, or humanize writing. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| whyykorovko/dotagentsInvestigate why code or a design exists using repository history and available contextual sources. Use only when the user explicitly asks about rationale, tradeoffs, regressions, historical constraints, or the origin of a threshold or behavior. | Stars: 0 | Updated | Claude CodeCodex | Verified | Install |
| html-designNimaChu/html-designCreate, redesign, repair, validate, preview, and package lightweight standalone HTML deliverables. Use for marketing experiences, product prototypes, infographics, motion narratives, documents, browser tools, dashboards, guided workflows, knowledge interfaces, mini-games, presentations, reusable style and brand systems, and local-model text, vision, image, or code tools that must run without a build chain or hosted service. | Stars: 99 | Updated | Claude CodeCodex | Verified | Install |
| balanced-couplingvladikk/modularityThe Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions. | Stars: 604 | Updated | Claude CodeCodex | Verified | Install |
| designvladikk/modularityDesigns modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications. | Stars: 604 | Updated | Claude CodeCodex | Verified | Install |
| documentvladikk/modularityProduces modularity review documents in both Markdown and HTML formats. Use when writing the final review output from a modularity analysis. | Stars: 604 | Updated | Claude CodeCodex | Verified | Install |
| reviewvladikk/modularityAnalyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive. | Stars: 604 | Updated | Claude CodeCodex | Verified | Install |
| ghm-gate-checkmattgierhart/PRD-driven-context-engineeringValidates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check`. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-harvestmattgierhart/PRD-driven-context-engineeringExtracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-id-registermattgierhart/PRD-driven-context-engineeringValidates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-self-installmattgierhart/PRD-driven-context-engineeringInstall the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-sot-buildermattgierhart/PRD-driven-context-engineeringCreates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-status-syncmattgierhart/PRD-driven-context-engineeringSynchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| ghm-template-syncmattgierhart/PRD-driven-context-engineeringDetect template version drift and guide migration to the latest template version. Compares current repo against the template, identifies what's outdated, and automates safe updates while protecting product-specific content. Triggers on requests to sync with template, update template version, check for template drift, or when user asks "sync template", "update to v3", "template drift", "check template version". | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| initmattgierhart/PRD-driven-context-engineeringSeed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v01-problem-framingmattgierhart/PRD-driven-context-engineeringTransform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v01-user-value-articulationmattgierhart/PRD-driven-context-engineeringTransform validated pain points into articulated user value statements for PRD v0.1 Spark. Triggers on completing problem framing, defining user outcomes, articulating value propositions, or requests like "what value do users get", "define outcomes", "articulate the benefit", "finish v0.1", "pain to value", "what do they gain". Outputs CFD- entries tagged as value hypotheses with evidence tiers. Follows Problem Framing skill in workflow. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v02-competitive-landscape-mappingmattgierhart/PRD-driven-context-engineeringMap the competitive landscape before positioning your product for PRD v0.2 Market Definition. Triggers on completing v0.1 Spark, analyzing competitors, researching market, or requests like "competitive analysis", "who else solves this", "market landscape", "what alternatives exist", "competitor research", "feature comparison". Outputs CFD- entries for competitive intelligence and BR- entries for positioning rules. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v02-product-type-classificationmattgierhart/PRD-driven-context-engineeringClassify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v03-features-value-planningmattgierhart/PRD-driven-context-engineeringDefine and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v03-moat-definitionmattgierhart/PRD-driven-context-engineeringAssess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v03-outcome-definitionmattgierhart/PRD-driven-context-engineeringDefine measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v03-pricing-modelmattgierhart/PRD-driven-context-engineeringSelect and validate pricing model for PRD v0.3 Commercial Model. Triggers on requests to set pricing, choose monetization model, design pricing tiers, validate willingness to pay, or when user asks "how much should we charge?", "what pricing model?", "freemium vs paid?", "how to structure tiers?", "price point?". Consumes Competitive Landscape (CFD-) and Product Type (BR-) from v0.2. Outputs BR- entries for pricing rules, tier boundaries, and competitive positioning. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v04-persona-definitionmattgierhart/PRD-driven-context-engineeringSynthesize behavioral personas from prior stage evidence for journey mapping and marketing during PRD v0.4 User Journeys. Triggers on requests to define personas, create user profiles, identify target users, or when user asks "who are our users?", "define personas", "user profiles", "target users", "persona creation", "who uses this product?". Consumes CFD- (v0.1-v0.3), BR- (targeting from v0.3 Moat), FEA- (v0.3 Feature Value Planning). Outputs PER- entries with behavioral profiles and feature relationships. Feeds v0.4 User Journey Mapping. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v04-screen-flow-definitionmattgierhart/PRD-driven-context-engineeringConnect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |
| prd-v04-user-journey-mappingmattgierhart/PRD-driven-context-engineeringMap user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition. | Stars: 179 | Updated | Claude CodeCodex | Verified | Install |