New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Prd V10 Chasm Adoption Moore

by mattgierhart in mattgierhart/PRD-driven-context-engineering

Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption.

MITAuto-check passedProduct & Project Management

Install Prd V10 Chasm Adoption Moore

skills CLI
$ npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-chasm-adoption-moore -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mattgierhart/PRD-driven-context-engineering prd-v10-chasm-adoption-moore --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prd-v10-chasm-adoption-moore .claude/skills/prd-v10-chasm-adoption-moore && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd-v10-chasm-adoption-moore
GitHub stars
180
Token cost
~3.2k tokens
SKILL.md length
1,474 words
Files
1
Skills in repo
45
Repo updated
First seen
Licence
MIT

At a glance

Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption.

  • Works in 5 steps: Assess current adoption stage → Pick the beachhead segment [standard+] → Whole-product gap analysis → …
  • Requests to assess adoption stage
  • SKILL.md covers Execution Mode, Framework: Moore's Technology…, Consumes and Produces, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd V10 Chasm Adoption Moore is an agent skill from mattgierhart/PRD-driven-context-engineering. Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption. Triggers on requests to assess adoption stage, plan beachhead, cross the chasm, scale from early adopters, or when user asks "are we in the chasm?", "crossing the chasm", "beachhead strategy", "Moore", "whole product", "pragmatist buyers", "from early adopters to early majority". Outputs ADO-STAGE-, ADO-BEACHHEAD-, ADO-WHOLE-, ADO-REF- entries.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD… The licence is MIT.

When your agent uses it

  • Requests to assess adoption stage
  • Cross the chasm
  • Scale from early adopters
  • User asks are we in the chasm?

Example prompts

  • “are we in the chasm?”
  • “crossing the chasm”
  • “beachhead strategy”
  • “/prd-v10-chasm-adoption-moore”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, WebSearch

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Assess current adoption stage
  2. Pick the beachhead segment [standard+]
  3. Whole-product gap analysis
  4. Reference-account cultivation plan [standard+]
  5. Chasm-crossing risk register [deep only]

What it can do on your machine

Read from SKILL.md and the folder at commit 30ed1b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd V10 Chasm Adoption Moore loads about 3.2k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 1,474 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~138
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mattgierhart/PRD-driven-context-engineering at commit 30ed1b0, republished under its MIT licence (© mattgierhart). 1,474 words, ~3,239 tokens.

Download SKILL.mdSave it as .claude/skills/prd-v10-chasm-adoption-moore/SKILL.md (or your agent's skills folder).
name
prd-v10-chasm-adoption-moore
description
Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption. Triggers on requests to assess adoption stage, plan beachhead, cross the chasm, scale from early adopters, or when user asks "are we in the chasm?", "crossing the chasm", "beachhead strategy", "Moore", "whole product", "pragmatist buyers", "from early adopters to early majority". Outputs ADO-STAGE-*, ADO-BEACHHEAD-*, ADO-WHOLE-*, ADO-REF-* entries.
allowed-tools
Read, Write, Edit, Glob, Grep, WebSearch
context
fork
execution_modes.default
deep
execution_modes.supports
quick, standard, deep

Crossing the Chasm (Moore) — the v1.0 Spine

Position in workflow: v0.9 Feedback Loop Setup → v1.0 Crossing the Chasm (Moore) → all v1.0 work

Execution Mode

Default is deep (this is a major strategic decision; quick mode is for hypothesis pre-work only). See .claude/rules/08-skill-execution-modes.md.

ModeWhat this skill produces
quickStage assessment only (ADO-STAGE-*); beachhead candidate hypothesis
standardStage assessment + beachhead segment + top 3 whole-product gaps + reference-account candidate list
deep (default)Full stage assessment with evidence + sharpened beachhead with in/not-in criteria + complete whole-product gap analysis + reference-account cultivation plan + chasm-crossing risk register

Framework: Moore's Technology Adoption Lifecycle

From Crossing the Chasm (Geoffrey Moore, 1991, updated 2014). The bestselling tech-strategy book of the 1990s, and still the canonical model for understanding why early traction doesn't predict mass adoption.

The lifecycle
Stage% of marketBuyer mindsetWhat they buy
Innovators (2.5%)Tinkerers; technology enthusiastsWant to try new things; tolerate incomplete productsVision, technical depth, access
Early Adopters (13.5%)VisionariesWant strategic advantage from non-mainstream techBold vision + first-mover ROI
— THE CHASM ————
Early Majority (34%)PragmatistsWant reliable productivity gains from proven solutionsWhole product + segment-specific references
Late Majority (34%)ConservativesWant safe, mature defaultsMarket leadership, low risk
Laggards (16%)SkepticsResist change(Generally not worth targeting)
The chasm

The gap between Early Adopters and Early Majority is the chasm. Most products die here. The reason: visionary buyers (who got you to early traction) actively want the cutting-edge, while pragmatist buyers want to be the second penguin off the iceberg — they need to see peers in their segment succeeding first.

The chasm-crossing playbook
  1. Pick a beachhead segment — A single, narrowly-defined sub-segment of the early majority. Not "small businesses." Specific: "freight-forwarding firms with 50-200 employees in the US Pacific Northwest using ERP X."
  2. Build the whole product for that beachhead — Pragmatists don't buy your core product; they buy your core + integrations + reference customers + support + training + everything else they need to deploy. Identify and close the gaps.
  3. Cultivate references in segment — A reference from outside the beachhead is worthless to a beachhead buyer. Three references inside the beachhead is the unlock.
  4. Concentrate, then expand — Don't try to cross the chasm broadly. Win the beachhead, then use it as a reference base to win adjacent segments ("bowling alley" stage).

Consumes

  • CFD-* customer evidence (all stages, especially v0.9 post-launch feedback) — Composition of paying customers; stage signal
  • PER-* personas (sharpened by v0.9 Positioning) — Beachhead is a sharper variant of an existing PER-
  • GTM-* positioning (from v0.9 Positioning) — Best-fit segment is the starting point for beachhead selection; beachhead is usually tighter
  • GTM-* offer card (from v0.9 Offer Construction) — Offer must match beachhead expectations (pragmatists need different guarantees than visionaries)
  • FEA-* features (from v0.3) — Whole-product gap analysis cross-references current feature set
  • KPI-* baseline metrics (from v0.3 + v0.9) — Stage assessment uses retention shape, NPS by segment, conversion rate
  • BR-PRICING-* (from v0.3 + v0.9) — Pragmatist buyers expect different pricing/contract terms than visionaries

Produces

  • ADO-STAGE-* entries in SoT/SoT.ADOPTION.md — Current adoption-stage assessment with evidence
  • ADO-BEACHHEAD-* entries — Beachhead segment definition with strict in/not-in criteria
  • ADO-WHOLE-* entries — Whole-product gaps (one per gap, with owner and close date)
  • ADO-REF-* entries — Reference-account targets (one per candidate, with consent + placement status)
  • CFD-* gaps surfaced — When stage evidence is thin or beachhead selection lacks data, log as research gaps

Execution

Step 1: Assess current adoption stage

Audit current paying-customer composition. For each customer, classify by stage indicators:

IndicatorInnovator/Early AdopterEarly Majority
Sales motionDirect founder relationshipAsked for demo / pricing / case studies
Setup tolerance"I'll figure it out""Show me the integration with X"
Reference needNoneAsked "who else in my industry uses this?"
Renewal motivation"We're betting on this""It saves us $X/month"
ProcurementSingle buyerProcurement / SOC2 / contracts review

Stage signal:

  • Innovators / Early Adopters: >70% of paid customers show visionary indicators
  • At the chasm: Mixed composition; new inbound asking pragmatist questions ("references", "integrations", "SOC2"); flat MRR despite growing leads
  • Bowling Alley (post-chasm): >50% of new customers in one identifiable segment
  • Tornado: Rapid acquisition across multiple segments
  • Main Street: Stable growth, focus on expansion and retention

Deliverable: One ADO-STAGE-* entry with evidence, stage classification, and confidence score.

Step 2: Pick the beachhead segment [standard+]

Generate 3–5 candidate beachhead segments. Score each:

CriterionQuestionWeight
Pragmatist densityIs this segment mostly pragmatists (already buying mature solutions)?High
Whole-product proximityHow close is our current product to the segment's whole-product expectation?High
Reference accessibilityCan we get 3 references in this segment within 6 months?High
Compelling reason to buyIs there an urgent, segment-specific pain we solve uniquely?High
Adjacency valueIf we win this segment, what adjacent segments unlock?Medium
Competitive intensityHow saturated is this segment with established competitors?Medium
Market sizeIs this segment large enough to support a beachhead?Low (most beachheads are small; that's fine)

Pick the top-scoring segment. Write strict in-segment and not in-segment criteria.

Deliverable: One ADO-BEACHHEAD-* entry with in/not-in criteria, rationale, target (e.g., "10 closed-won in segment within 6 months"), confidence.

Step 3: Whole-product gap analysis

For the beachhead segment, list everything a pragmatist buyer in that segment expects to receive when they pay you:

  • Core product (what you ship)
  • Integrations (with their existing stack — specific)
  • Compliance (SOC2, HIPAA, ISO — segment-specific)
  • Support (response-time SLA, dedicated CSM if appropriate)
  • Training / onboarding (videos, docs, certifications)
  • References (segment-specific, named, willing to talk)
  • Pricing / contract terms (annual contracts, MSAs, custom DPAs)
  • Migration / data import
  • Professional services (implementation help)
  • Roadmap visibility

For each, score: Ship today? / Gap?

For each gap, create an ADO-WHOLE-* entry with severity (blocker / serious / nice-to-have), owner, target close date.

Deliverable: List of ADO-WHOLE-* entries. Blockers must close before sustained beachhead motion.

Show full SKILL.md (542 more words)Show less
Step 4: Reference-account cultivation plan [standard+]

Identify 5–10 existing or near-term customers in the beachhead segment that could become public references. For each:

FieldNotes
CustomerName + segment fit confirmation
Story strengthWhat outcome can they speak to publicly? (Quantified > qualitative)
RelationshipWho owns the relationship internally?
Consent pathWhat approval do they need internally to be public?
Target placementLogo on pricing page / quote on landing / blog case study / on-stage / podcast
Confidence1–5 of "will become a reference within 90 days"

Deliverable: 5–10 ADO-REF-* entries with cultivation plan.

Step 5: Chasm-crossing risk register [deep only]

For each major chasm risk, log a RISK-* entry:

  • Reference-cold risk — Can't get 3 references in beachhead within 6 months
  • Whole-product gap risk — Critical gap can't be closed in time
  • Beachhead-too-small risk — Segment doesn't sustain the company economically even if won
  • Competitor-incumbency risk — Pragmatist defaults are competitor X; switching cost too high
  • Internal motion risk — Sales / support / product can't pivot from visionary motion to pragmatist motion

Each risk gets mitigation actions tied to ADO-WHOLE-, ADO-REF-, or BR-* updates.

Deliverable (deep): Risk register with mitigations.

Output Templates

See SoT/SoT.ADOPTION.md for the complete entry templates for ADO-STAGE-, ADO-BEACHHEAD-, ADO-WHOLE-, and ADO-REF-.

Anti-Patterns

PatternSignalFix
"We're in the chasm" without evidenceStage assessment based on vibesAudit actual paying-customer composition; require ADO-STAGE-* confidence ≥ 3/5
Beachhead too broad"Small businesses" or "B2B SaaS"Tighten until it disqualifies most buyers; segment of 100–10,000 prospects max
Skipping whole-product gap"Our product is great; we just need more marketing"Pragmatists buy whole product, not core product; list every gap
Reference from wrong segmentTouting a visionary customer to a pragmatist buyerIn-segment references only; cross-segment is worthless
Crossing the chasm broadly"Let's just scale paid ads"Concentrate on beachhead; broad CAC will be 5× higher and worse-converting
Confusing best-fit with beachheadTreating Dunford best-fit as the beachheadBeachhead is tighter than best-fit; usually one sub-segment of the best-fit
Skipping stage assessmentJumping to "we need to scale" without checking where we areStep 1 is mandatory; without it, the rest is guesswork

Quality Gates

Before proceeding to other v1.0 work:

  • ADO-STAGE-* entry exists with evidence and confidence ≥ 3/5
  • If stage is "at the chasm" or beyond: ADO-BEACHHEAD-* defined with strict in/not-in criteria
  • At least 3 ADO-WHOLE-* gap entries identified (blockers + serious)
  • At least 3 ADO-REF-* candidate accounts (standard+)
  • RISK-* entries cover the top chasm risks (deep only)
  • Beachhead does not contradict v0.9 Positioning's best-fit (or contradiction is explicit and rationalized)

Downstream Connections

ConsumerWhat it usesExample
Continuous Discovery (Torres)Beachhead segment = discovery interview poolWeekly interviews drawn from ADO-BEACHHEAD-
Mom Test InterviewBeachhead-segment interview disciplineValidate ADO-STAGE- and ADO-WHOLE- via Mom Test
Case Study BuilderReference candidates = case study targetsADO-REF-* graduates to case study
Testimonial CollectorReference candidates = testimonial targetsADO-REF-* (lower-effort placement)
v0.9 Re-runsBeachhead may sharpen Positioning; whole-product gaps may shift OfferRe-run Dunford with sharper segment
Feedback Loop SetupPragmatist-shaped feedback signals chasm crossingInbound pattern shift → re-run stage assessment

Detailed References

  • Geoffrey Moore, Crossing the Chasm (1991, revised 2014) — canonical source
  • Geoffrey Moore, Inside the Tornado (1995) — post-chasm bowling alley / tornado / main street
  • Eric Ries, The Lean Startup (incompatible motion before chasm; useful contrast)
  • wondelai's crossing-the-chasm skill (wondelai/skills)
  • (No bundled references/ — read the book for depth)

© mattgierhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/prd-v10-chasm-adoption-moore of mattgierhart/PRD-driven-context-engineering.

Open the folder on GitHubat commit 30ed1b0

Compare with similar skills

Prd V10 Chasm Adoption Moore next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd V10 Chasm Adoption Moore compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd V10 Chasm Adoption Moore this skillmattgierhart/PRD-driven-context-engineering180—~3.2kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Trellis Brainstormanjiemo/SunnyBeach1787 repos~4kAutomated safety check: PassApache-2.0
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
Ralph Tui Create JSONsubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Prd Generator

    jamesrochabrun/skills

    Generate comprehensive Product Requirements Documents (PRDs) for product managers.

    216 GitHub starsUsed in 2 repos~3.8k tokens
    Product & Project ManagementAuto-check passed

More from mattgierhart/PRD-driven-context-engineering

All 45 skills in this repo

  • Ghm Gate Check

    mattgierhart/PRD-driven-context-engineering

    Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py).

    180 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes

  • Ghm Harvest

    mattgierhart/PRD-driven-context-engineering

    Extracts durable insights from temp/ files to SoT during EPIC Phase E.

    180 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Ghm Id Register

    mattgierhart/PRD-driven-context-engineering

    Validates and registers new SoT IDs with cross-reference integrity.

    180 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Ghm Sot Builder

    mattgierhart/PRD-driven-context-engineering

    Creates new Source of Truth (SoT) files when existing templates don't fit your needs.

    180 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Prd V01 Problem Framing

    mattgierhart/PRD-driven-context-engineering

    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark.

    180 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Prd V01 User Value Articulation

    mattgierhart/PRD-driven-context-engineering

    Transform validated pain points into articulated user value statements for PRD v0.1 Spark.

    180 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Prd V10 Chasm Adoption Moore

What does Prd V10 Chasm Adoption Moore do?

Assess adoption-lifecycle stage, plan the chasm crossing, and build a beachhead strategy using Geoffrey Moore's Crossing the Chasm framework during PRD v1.0 Market Adoption. Prd V10 Chasm Adoption Moore is an agent skill from mattgierhart/PRD-driven-context-engineering.0 Market Adoption.

When should I use Prd V10 Chasm Adoption Moore?

Prd V10 Chasm Adoption Moore fits situations like: requests to assess adoption stage; cross the chasm; scale from early adopters; user asks are we in the chasm?.

How do I install Prd V10 Chasm Adoption Moore in Claude Code?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-chasm-adoption-moore -a claude-code`. Or copy the skill folder (.claude/skills/prd-v10-chasm-adoption-moore in mattgierhart/PRD-driven-context-engineering) into .claude/skills/prd-v10-chasm-adoption-moore in your project. Claude Code loads it when a task matches its description.

How do I install Prd V10 Chasm Adoption Moore in Codex?

Run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-chasm-adoption-moore -a codex`. Or copy the skill folder (.claude/skills/prd-v10-chasm-adoption-moore in mattgierhart/PRD-driven-context-engineering) into .agents/skills/prd-v10-chasm-adoption-moore in your project. Codex loads it when a task matches its description.

Can I use Prd V10 Chasm Adoption Moore in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v10-chasm-adoption-moore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd-v10-chasm-adoption-moore, .gemini/skills/prd-v10-chasm-adoption-moore, .github/skills/prd-v10-chasm-adoption-moore and .opencode/skills/prd-v10-chasm-adoption-moore in your project.

What does Prd V10 Chasm Adoption Moore need to run?

SKILL.md names no scripts, command-line tools or credentials: Prd V10 Chasm Adoption Moore is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, WebSearch.

Does Prd V10 Chasm Adoption Moore access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prd V10 Chasm Adoption Moore safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd V10 Chasm Adoption Moore use?

Prd V10 Chasm Adoption Moore is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd V10 Chasm Adoption Moore use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prd V10 Chasm Adoption Moore?

Skills that share tags, products or a category with Prd V10 Chasm Adoption Moore: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd V10 Chasm Adoption Moore?

mattgierhart (a GitHub user) maintains it in mattgierhart/PRD-driven-context-engineering, which has 180 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on August 31, 2026.

Source: mattgierhart/PRD-driven-context-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.