Lean Startup
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead…
Install Discovery Drafting
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install danjdewhurst/story-skills discovery-drafting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/discovery-drafting .claude/skills/discovery-drafting && rm -rf skills-srcUse ~/.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/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .claude/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-draftingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install danjdewhurst/story-skills discovery-drafting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/discovery-drafting .agents/skills/discovery-drafting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .agents/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install danjdewhurst/story-skills discovery-drafting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/discovery-drafting .cursor/skills/discovery-drafting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .cursor/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/danjdewhurst/story-skills.git --path skills/discovery-drafting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install danjdewhurst/story-skills discovery-drafting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/discovery-drafting .gemini/skills/discovery-drafting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .gemini/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install danjdewhurst/story-skills discovery-draftingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/discovery-drafting .github/skills/discovery-drafting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .github/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danjdewhurst/story-skills --skill discovery-drafting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install danjdewhurst/story-skills discovery-drafting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danjdewhurst/story-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/discovery-drafting .opencode/skills/discovery-drafting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "discovery-drafting" agent skill from https://github.com/danjdewhurst/story-skills/tree/main/skills/discovery-drafting into .opencode/skills/discovery-drafting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-drafting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
discovery-drafting- GitHub stars
- 279
- Used in
- 1 other repo
- Token cost
- ~2k tokens
- SKILL.md length
- 1,000 words
- Files
- 5 (incl. references)
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MIT
At a glance
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead…
- Works in 6 steps: Write the story kernel. Consult… → Draft forward. Create the chapter with → Run the reconcile loop. After each… → …
- Asks about pantsing
- SKILL.md covers Overview, Prerequisites, When to Use and Workflow, plus 4 more sections
- Calls node
What it does
Discovery Drafting is an agent skill from danjdewhurst/story-skills. This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/dead-ends.md`, `references/drafting-cadence.md` and `references/reconcile-loop.md`).
It sits in Business, Finance & HR, covering Accounting and bookkeeping, Retrospectives and Creative writing and fiction. The repository describes itself as: Agent Skills for end-to-end story writing in markdown, packaged as Codex and Claude Code plugins. The licence is MIT.
When your agent uses it
- Asks about pantsing
- Discovery write
- Write without an outline
- Discovery draft
Example prompts
- “pantsing”
- “discovery write”
- “write without an outline”
- “/discovery-drafting”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Write the story kernel. Consult references/story-kernel.md and
- Draft forward. Create the chapter with
- Run the reconcile loop. After each chapter, follow
- Batch review every 3–5 chapters. Re-read post-hoc notes, sweep the
- Hold the cadence. Keep the agreed target (see
- Close the loop on mode. When the draft is complete, every
What it can do on your machine
Read from SKILL.md and the folder at commit 1df23f9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
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
Discovery Drafting loads about 2k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 1,000 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:104
`bunfig.toml` (which can run code) and `.env`, and a package script runs from the checkout's root. If no CLI is availab
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 danjdewhurst/story-skills at commit 1df23f9, republished under its MIT licence (© danjdewhurst). 1,000 words, ~2,028 tokens.
Download SKILL.mdSave it as
.claude/skills/discovery-drafting/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- discovery-drafting
- description
- This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
Discovery Drafting
Overview
Draft by discovery ("pantsing"): start from a one-paragraph story kernel rather than a beat sheet, write forward, then reconcile each chapter back into the story bible through a structured loop (extract entities → reverse outline → diff against the bible → reconcile). This is the complement to chapter-writing's outline-first workflow. The bible is maintained after the prose, not before — which the repo's import-style entity extraction and continuity checks already support.
Prerequisites
A story project must already exist (created via the story-init skill), with
at least a story.md and one character. No plot structure is required to
start — arcs get built during reconciliation.
When to Use
- The user wants to draft without outlining first, or identifies as a discovery writer
- Starting a project from a situation/character rather than a plot
- NOT for mysteries or other clue-dependent genres where setup must precede
payoff (use chapter-writing; see
genre-craft) - NOT for revising existing chapters, including a reverse outline of an
existing linear draft or cutting a subplot as a revision pass (use
revision-continuity). The reverse outline inside the reconcile loop, and cutting dead ends in a batch review, stay here - The user can switch modes per project or per chapter; record the mode so audits know which discipline applies
Workflow
- Write the story kernel. Consult
references/story-kernel.mdand draft the one-paragraph kernel with the user (character in a situation, a want, an obstacle, a tone signal). Store it instory.mdunder## Story Kerneland setdraft-mode: discoveredin frontmatter. - Draft forward. Create the chapter with
story add chapter 'Title' --number N --mode discoveredsostory nextflags it until it is reconciled (in adraft-mode: discoveredproject a drafted chapter with nomodeis flagged too). Write the chapter from the kernel using the session shape inreferences/drafting-cadence.md(re-read → write → close with a next-session note). Write forward only; park bible questions as[TODO: check bible]inline rather than stopping. Follow the prose craft inchapter-writing/references/writing-guidelines.mdand the scene-grain tools in thescene-craftskill as usual, and write in the voice and house style recorded instyle-sheet.md— discovery changes planning order, not prose standards. Write in thelanguageset instory.md(a missing field meansen); the craft references' word-level advice is English, so in another language keep its aims and follow the style sheet's conventions. - Run the reconcile loop. After each chapter, follow
references/reconcile-loop.mdexactly:- Extract new entity/promise candidates (import-style, user-approved),
keeping names as the prose spells them. Ids stay ASCII kebab-case:
Cyrillic and Greek names get one automatically (
Пётрgivespetr), and a name in a script with no transliteration table (李明) needsstory add character '李明' --id li-ming, with the id agreed with the user - Reverse-outline the chapter into the chapter file and
scenes/records - Diff against the bible (new / contradiction / enrichment / dangling)
- Reconcile: update the bible or revise the chapter — never neither
- Add post-hoc chapter notes above
## Chapter Text(below it they count and ship as prose); set chapter frontmattermode: discovered
- Extract new entity/promise candidates (import-style, user-approved),
keeping names as the prose spells them. Ids stay ASCII kebab-case:
Cyrillic and Greek names get one automatically (
- Batch review every 3–5 chapters. Re-read post-hoc notes, sweep the
promise/question ledgers for dangling setups, and cut dead ends per
references/dead-ends.md(abandoned ledger entries keep a recorded reason; cut characters getstatus: cut, not deletion). - Hold the cadence. Keep the agreed target (see
references/drafting-cadence.md) and log each session withstory progress . --log; at midpoint and draft completion, hand the batch torevision-continuityfor developmental checks before continuing. - Close the loop on mode. When the draft is complete, every
mode: discoveredchapter must have post-hoc notes and a completed diff —story nextlists any without post-hoc notes underReconcile discovered chapters; finish those, then hand the manuscript torevision-continuityfor revision passes.
Show full SKILL.md (393 more words)Show less
Conventions
story.mdfrontmatterdraft-mode: discoveredmarks a discovery project; per-chaptermode: discovered/mode: outlinedtracks mixed projects.- Chapters carry a
## Chapter Notes (post-hoc)section, above## Chapter Text, recording what was discovered, what was cut, and open questions — the project's memory of why the bible looks the way it does. - Entity candidates extracted from prose are presented for user approval
before bible files are created (same discipline as
story import). - Cut threads are logged, not erased: abandoned promises/questions keep
status: abandonedwith a reason; cut characters keep their file withstatus: cut. - Bidirectional links and kebab-case ids follow the shared story conventions exactly — discovery changes when the bible is written, not how.
CLI Maintenance
Use the Story CLI when it is available. If story is not installed, use the bundled fallback node ../story-maintenance/scripts/story.js with the same arguments. Use node <checkout>/bin/story.js instead only when the user names a Story Skills repository checkout or you are working in one. Write the script as an absolute path (resolve the fallback relative to this skill folder) and run it from the folder you would run story from, so . and other relative paths keep their meaning. Use Node, not Bun or a package script: Bun would load that folder's bunfig.toml (which can run code) and .env, and a package script runs from the checkout's root. If no CLI is available, perform the registry, backlink, and word-count checks manually.
After each reconcile loop:
story reindex .
story wordcount . --write
story check .Reference Files
references/story-kernel.md- The one-paragraph kernel: character in a situation, want, obstacle, tone signalreferences/reconcile-loop.md- The core loop: extract entities/promises → reverse-outline → diff against the bible → reconcile;mode: discoveredflagreferences/dead-ends.md- Recognizing and cutting dead ends: cut/fold/prune, abandoned ledger entries, the darling logreferences/drafting-cadence.md- Daily targets, batch reviews, session shape, recovering a broken cadence
Shared Conventions
Every story skill follows the shared conventions in ../story-maintenance/references/conventions.md, resolved relative to this skill folder. Read it before creating, renaming, or linking story files. If that file is missing because this skill was installed without story-maintenance, the essentials are: kebab-case ids and filenames, YAML frontmatter on every story-project file, _index.md registry tables that story reindex rebuilds (never edit them by hand), bidirectional links between entities, characters for who is on the page and mentions for who is only referred to, status: deceased plus died-in: chapter-{NN} for deaths, and no project-local generator or build scripts (run only the installed or bundled Story CLI).
© danjdewhurst, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/discovery-drafting of danjdewhurst/story-skills.
- SKILL.md
- references/dead-ends.md
- references/drafting-cadence.md
- references/reconcile-loop.md
- references/story-kernel.md
Open the folder on GitHubat commit 1df23f9
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in danjdewhurst/story-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Discovery Drafting 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Discovery Drafting this skilldanjdewhurst/story-skills | 279 | 1 repos | ~2k | Automated safety check: Notes | MIT | |
| Lean Startupgetagentseal/founder-playbook | 724 | — | ~4.6k | Automated safety check: Pass | MIT | |
| Lean Startupwondelai/skills | 2.4k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Longbridge Value Investinghelsome/folio | 269 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence |
Similar skills
Lean Startup
wondelai/skills
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn.
Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
Longbridge Value Investing
helsome/folio
Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
More from danjdewhurst/story-skills
All 24 skills in this repoAdaptation
danjdewhurst/story-skills
This skill should be used when the user asks to "make an audiobook", "narration script", "narrator", "ACX", "Findaway", "pronunciation guide", "how long is the audiobook", "adapt to a screenplay"…
Story Maintenance
danjdewhurst/story-skills
This skill should be used when the user asks to "validate", "reindex", "repair registries", "check links", "run the continuity, pacing, clue, voice, or name checks", "count words", "summarize a…
Research
danjdewhurst/story-skills
This skill should be used when the user asks to "research", "fact-check", "check the history", "is this accurate", "research notes", "sources", "historical accuracy", "technical accuracy", "how…
Chapter Writing
danjdewhurst/story-skills
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write…
Character Management
danjdewhurst/story-skills
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character…
Editorial Review
danjdewhurst/story-skills
This skill should be used when the user asks for a "sensitivity reader", "authenticity reader", "cultural review", "is this portrayal okay", "real people in my novel", "defamation", "can I use song…
Related
Questions about Discovery Drafting
What does Discovery Drafting do?
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead…. Discovery Drafting is an agent skill from danjdewhurst/story-skills. This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation.
When should I use Discovery Drafting?
Discovery Drafting fits situations like: asks about pantsing; discovery write; write without an outline; discovery draft.
How do I install Discovery Drafting in Claude Code?
Run `npx skills add danjdewhurst/story-skills --skill discovery-drafting -a claude-code`. Or copy the skill folder (skills/discovery-drafting in danjdewhurst/story-skills) into .claude/skills/discovery-drafting in your project. Claude Code loads it when a task matches its description.
How do I install Discovery Drafting in Codex?
Run `npx skills add danjdewhurst/story-skills --skill discovery-drafting -a codex`. Or copy the skill folder (skills/discovery-drafting in danjdewhurst/story-skills) into .agents/skills/discovery-drafting in your project. Codex loads it when a task matches its description.
Can I use Discovery Drafting 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 danjdewhurst/story-skills --skill discovery-drafting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discovery-drafting, .gemini/skills/discovery-drafting, .github/skills/discovery-drafting and .opencode/skills/discovery-drafting in your project.
What does Discovery Drafting need to run?
Going by SKILL.md and its folder, Discovery Drafting needs the command-line tools its instructions call (node).
Does Discovery Drafting 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 Discovery Drafting safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Discovery Drafting use?
Discovery Drafting 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 Discovery Drafting use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.
What are the alternatives to Discovery Drafting?
Skills that share tags, products or a category with Discovery Drafting: Lean Startup (getagentseal/founder-playbook, 724 stars), Lean Startup (wondelai/skills, 2.4k stars), Sync Upstream (nyaruka/phonenumbers, 1.6k stars) and Longbridge Value Investing (helsome/folio, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discovery Drafting?
danjdewhurst (a GitHub user) maintains it in danjdewhurst/story-skills, which has 279 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 8, 2026.
Source: danjdewhurst/story-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.