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 ehlyzov/skills --skill product-workflowgit clone --depth 1 https://github.com/ehlyzov/skillsWrote 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/ehlyzov/skills/product-workflow)<a href="https://agentmods.dev/skills/ehlyzov/skills/product-workflow"><img src="https://agentmods.dev/badge/skills/ehlyzov/skills/product-workflow/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/ehlyzov/skills/product-workflow"><img src="https://agentmods.dev/badge/skills/ehlyzov/skills/product-workflow.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.00066 | $0.09244 |
| Opus 5 | $0.00033 | $0.04622 |
| Sonnet 5 | $0.00013 | $0.01849 |
| Haiku 4.5 | $0.00007 | $0.00924 |
Grade A, and why
product-workflow 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Workflow
Скилл создаёт продуктовые документы и планы. Он не исполняет утверждённый технический план и не управляет обычной разработкой. Выбирай только те артефакты и фазы, которые пользователь запросил явно; полный пакет не является режимом по умолчанию.
Возможные выходы:
- Продуктовое описание (
docs/product/overview.md+docs/product/scenarios/01..N.md) — задача, персоны, проблемы, цели, N сценариев по строгому шаблону. - Журнал решений (
docs/product/decisions.md) — варианты, факты, trade-offs, рекомендация агента и явный статус решения. - Baseline текущих сценариев (
docs/product/current-scenario-baseline.md+docs/product/scenario-cards.md+docs/product/scenario-graph.dot) — карта существующих сценариев, компактные пользовательские истории, страницы и переходы, если продукт уже существует или задача является доработкой. - Impact-документ инкремента (
docs/product/increments/<feature>-impact.md) — как новая фича расширяет, меняет или добавляет сценарии относительно baseline. - План реализации (
docs/plans/<product>-implementation-plan.md) — command-level задачи T0..TN для оркестратора + worker-а. - План усиления (
docs/plans/<product>-hardening-plan.md) — архитектура / безопасность / поддерживаемость, не добавляющая функционала; задачи H1..HN с зависимостями от T-задач. - Независимый вердикт и PDF (
docs/product/validation/verdict.md+ PDF в~/Downloads/) — stakeholder-facing продуктовый документ без T/H-планов по умолчанию.
Независимый верификатор обязателен только для полного PRD/delivery package, stakeholder PDF и явно запрошенного финального product gate. Для узкого режима он проверяет только созданный артефакт и его прямые источники. Не заставляй малую задачу оплачивать аудит полного продуктового архива.
Когда использовать
- Пользователь явно сказал: «нужно продуктовое описание», «PRD по фиче X», «спроектируй сценарии», «составь продуктовый план реализации», «hardening plan», «оформи продукт».
- Есть кодовая база и нужно зафиксировать её продуктовое лицо + roadmap.
- Нужно встроить новую фичу или доработку в уже существующий продукт, не создавая сценарный «остров».
- Есть идея/новый продукт без кода — нужно собрать целостную картину сценариев + план.
- Пользователь хочет один артефакт-PDF для шеринга со стейкхолдерами.
What ships with it
26 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.
- agents/explore-api.md 1.3 KB
- agents/explore-runtime.md 1.3 KB
- agents/explore-ui.md 1.2 KB
- agents/hardening-auditor.md 4.2 KB
- agents/implementation-verifier.md 2.1 KB
- agents/independent-verifier.md 6.6 KB
- agents/openai.yaml 278 B
- agents/plan-critic.md 4.3 KB
- agents/scenario-critic.md 3.4 KB
- agents/style-editor-en.md 1.4 KB
- agents/style-editor-ru.md 1.6 KB
- agents/ux-continuity-author.md 2.1 KB
- evals/evals.json 7.1 KB
- references/baseline-template.md 3.0 KB
- references/critic-checklist.md 6.4 KB
- references/decision-log-template.md 3.2 KB
- references/hardening-template.md 7.1 KB
- references/impact-pre-scan-template.md 3.0 KB
- references/increment-impact-template.md 3.4 KB
- references/overview-template.md 4.8 KB
- references/plan-template.md 8.9 KB
- references/product-pdf-template.md 2.6 KB
- references/scenario-card-template.md 2.9 KB
- references/scenario-template.md 6.6 KB
- scripts/build_pdf.sh 11 KB runs code
- scripts/verify_artifacts.py 39 KB runs code
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.
- 9d ago First seen · 438 lines · 66 tokens per session scan A 5411343f3168
product-workflow is a skill published in the GitHub repository ehlyzov/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 66 tokens to every session and 9,244 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…