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 tikalk/adlc-team-skills --skill factory-productgit clone --depth 1 https://github.com/tikalk/adlc-team-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/tikalk/adlc-team-skills/factory-product)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/factory-product"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/factory-product/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/tikalk/adlc-team-skills/factory-product"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/factory-product.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.00029 | $0.00933 |
| Opus 5.5 | $0.00012 | $0.00373 |
| Sonnet 5.5 | $0.00006 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
factory-product 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 15d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
factory-product
What this skill does
factory-product orchestrates the product-decisions lifecycle. It coordinates individual product-related skills (product-init, product-specify, product-clarify, product-implement, product-analyze) to maintain a consistent PRD.md at docs/adlc/product/PRD.md (ADR-401).
It operates as a Kind-A DAG orchestrator in alignment with the shared executor engine contract in factory-mission/references/executor.md.
When to use
- You want to bootstrap, refine, or analyze a product's requirements and decisions (PDRs) end-to-end.
- You want a guided, accept-gated, and verified product definition process with a resume checkpoint.
When NOT to use:
- For software implementation task execution (use
factory-missioninstead). - For architecture decision records (use
factory-architectinstead).
Lifecycle DAG & Step Resolution
factory-product implements a fixed named-skill DAG (fixed step resolution):
Greenfield Route (default on empty project)
specify(generatephase) -> Invokeproduct-specifyto collaboratively capture PDR drafts in.adlc/drafts/pdr/.clarify⭐ (clarifyphase) -> Invokeproduct-clarifyto run interactive quality checks and mark PDRs Accepted (human sign-off gate).implement(buildphase) -> Invokeproduct-implementto compile accepted PDRs intodocs/adlc/product/PRD.mdand promote them todocs/adlc/memory/pdr/.analyze(analyzephase) -> Invokeproduct-analyzeto verify PRD/PDR consistency and output a severity-ranked report.
Brownfield Route (default if code exists but no PDRs)
init(generatephase) -> Invokeproduct-initto reverse-engineer draft PDRs from the existing codebase.clarify⭐ →implement→analyze(same as Greenfield).
Refresh Route (default if PRD.md and memory PDRs already exist)
analyze(analyzephase) -> Run product-analyze first to detect drift.clarify⭐ →implement→analyze(drift-correction cycle).
What ships with it
1 file 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.
- 15d ago Changed 8303f8a793db
- 25d ago First seen · 61 lines · 29 tokens per session scan A da25b8a8cef8
factory-product is a skill published in the GitHub repository tikalk/adlc-team-skills (141 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 933 once invoked, about $0.0001 per session on Opus 5.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-21.
Other skills, from other repositories
batch-all-issues
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.
create-scrap-issue
Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.