Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add flanliulf/SpecLite --skill speclite-create-epics-and-storiesgit clone --depth 1 https://github.com/flanliulf/SpecLiteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/flanliulf/speclite/speclite-create-epics-and-stories)<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-create-epics-and-stories"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-create-epics-and-stories/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/flanliulf/speclite/speclite-create-epics-and-stories"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/speclite-create-epics-and-stories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.01091 |
| Opus 5 | $0.00041 | $0.00545 |
| Sonnet 5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
speclite-create-epics-and-stories scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
[技能说明] # Create Epics and Stories Workflow
**Goal:** 将 PRD、Architecture 与可选 UX Design 中的需求,拆解为按用户价值组织的 Epics 和可交付 Stories,并生成完整 `epics.md`。
**Your Role:** 产品策略师与技术规格撰写者,和产品负责人平等协作。
- 使用 `{communication_language}` 沟通,使用 `{document_output_language}` 生成文档。
- 你负责需求抽取、用户价值分组、故事粒度控制、验收标准和覆盖校验。
- 用户负责产品愿景、业务优先级、上下文确认和阶段性审批。
- 这是强交互工作流:禁止跳步,必须在菜单点 HALT 并等待用户选择。
[核心能力]
- 配置与激活解析:解析三层 customize(base→team→user)和 workflow 块,加载 persistent_facts、config.toml、激活前置/后置步骤和 workflow.on_complete。
- 输入制品发现与需求抽取:在 {planning_artifacts} 中按优先级发现 PRD、Architecture、可选 UX Design,抽取 FR、NFR、技术要求和 UX Design Requirements。
- Epic 设计协作:按用户价值而非技术层组织 Epic,显式处理 FR 覆盖、自然依赖、文件反复改动风险和合并边界。
- Story 顺序生成:逐个 Epic、逐个 Story 生成,确保每个 Story 可由单个开发智能体完成,且只依赖前置 Story。
- 模板化输出:从 assets/epics-template.md 初始化 {planning_artifacts}/epics.md,用 frontmatter 记录 stepsCompleted 与 inputDocuments。
- 最终覆盖校验:校验全部 FR、UX-DR、架构约束、实体创建时机、Epic 独立性与 Story 前向依赖。
[执行流程]
1. 先完整阅读 references/activation.md 与 references/workflow-steps.md;二者是完整操作规约,不能跳过或缩写执行。
2. 激活时解析 workflow、三层 customize、workflow.persistent_facts 与运行项目根下的 merged runtime config;本 Skill 目录中的 config.toml.example 仅作字段结构参考。
3. 使用 assets/epics-template.md 初始化输出文件,并严格按 references/workflow-steps.md 的 Step 1 → Step 4 顺序推进。
4. 每个步骤必须完整读取、顺序执行、保存状态;遇到菜单必须 HALT,只有用户选择 C 才能进入下一步。
5. 完成时保存 {planning_artifacts}/epics.md,执行 workflow.on_complete(若非空),并给出后续开发、Story 创建或评审建议。
[注意事项]
- 名称、目录与 YAML name 字段保持 kebab-case 一致:speclite-create-epics-and-stories。
- {speclite-runtime-root} 固定表示 {project-root}/_speclite;项目运行配置只通过 speclite resolve config --project-root {project-root} 读取 merged runtime config 中的。
- config.toml.example 只是参考示例,禁止作为 runtime fallback。
- customize.toml 只承载 [workflow] 默认定制面;团队和个人覆盖位于 {speclite-runtime-root}/custom/{skill-name}.toml 与 {skill-name}.user.toml。
- 不得替用户凭空生成需求;必须基于已发现文档和用户确认推进。
- Epic 必须按用户价值组织;Story 不得依赖同 Epic 中未来 Story,实体和表只在首次需要时创建。
- epics.md 末尾必须追加 *本文档由 speclite-create-epics-and-stories Skill 自动生成* 标注。
[生成信息] 本 Skill 由 speclite-skill-creator 自动生成。如需修改,建议同步更新 forge/ 和 .claude/skills/ 两份副本,或通过 skills-upgrade 管理版本。
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 48 lines · 82 tokens per session scan A e73239b12dcf
speclite-create-epics-and-stories is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,091 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
intake
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…
msg
Root menu for msg skills, plus harness modes. --init is the one-time project bootstrap — use it when the user says "initialise project", "bootstrap repo", "set up the framework", "start a new project", or asks to set up project structure in an empty repo. Other modes: --init-staging (add a staging branch), --update…
Scaleway Naming And Tagging
Scaleway naming convention and mandatory tags — resource-type abbreviations, region codes, and owner/cost-center/environment/workload tags for cost attribution.
plan-em
Engineering Manager skill. Reads an approved PRD, runs pre-flight checks against AHA.md, GLOSSARY.md and ARCHITECTURE.md, auto-runs plan-review certification inline (no ask), identifies specialist agents to activate (roster approval — the single human gate), spins them up to write engineering sections directly into…
plan-review
Staff PM contract certifier. Reads an existing PRD and runs a fixed seven-check certification — each check tied to a named downstream consumer (regression authoring, pre-merge's PRD-consistency gate, the safety pauses, eng --build's row/ticket reads). Product tune (--product) runs checks 1/2/3/6; eng tune (--eng) runs…
Incident Management
Severity classification, runbook structure, and blameless postmortems — so incidents are handled calmly, restored fast, and learned from.