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 product-implementgit 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/product-implement)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/product-implement"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/product-implement/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/product-implement"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/product-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.03916 |
| Opus 5 | $0.00030 | $0.01958 |
| Sonnet 5 | $0.00012 | $0.00783 |
| Haiku 4.5 | $0.00006 | $0.00392 |
Grade A, and why
product-implement 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 3d 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-implement
What this skill does
Transforms accepted PDRs into a comprehensive, self-contained PRD.md using a three-phase DAG:
- Plan Agent: Analyze PDRs, detect feature-areas, generate customized DAG, get user approval
- Execute Agent: Generate sections per feature-area with mandatory checkpoint after Requirements
- Summarize Agent: Aggregate sections, resolve conflicts, produce unified
PRD.md
Output:
PRD.md(repo root) — self-contained product requirements{REPO_ROOT}/.adlc/product/sections/{feature-area}/{section}.md— intermediate section files- Accepted PDRs moved to
{REPO_ROOT}/.adlc/memory/pdr/
When to use
- After
/product-clarifyhas approved PDRs - After
/product-initto document existing product - PDR updates requiring PRD regeneration
When NOT to use
- No Accepted PDRs (run
/product-clarifyfirst) - Minor PRD edits (edit
PRD.mddirectly)
Pre-Flight Validation
Before starting, verify prerequisites:
- Check PDRs exist:
{REPO_ROOT}/.adlc/drafts/pdr/PDR-*.md - Check for Accepted PDRs: Count files with status "Accepted"
- If zero: STOP and output:
Cannot proceed: No Accepted PDRs found. Run /product-clarify to review and approve PDRs first. - If ≥1: Proceed
- If zero: STOP and output:
Three-Phase DAG Workflow
┌─────────────────────────────────────────────────────────┐
│ PHASE 1: PLAN (Plan Agent) │
│ Load PDRs → Detect Feature-Areas → Generate DAG → Approve│
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ PHASE 2: EXECUTE (Execute Agent) │
│ Overview → Problem → Goals → Metrics → Personas │
│ → [REQUIREMENTS CHECKPOINT] ← MANDATORY USER APPROVAL │
│ → NFRs → Out-of-Scope → Risks → Roadmap → PDR-Summary │
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ PHASE 3: SUMMARIZE (Summarize Agent) │
│ Read sections → Detect conflicts → Resolve → PRD.md │
└─────────────────────────────────────────────────────────┘
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.
- scripts/bash/migrate-pdr-frontmatter.sh 8.7 KB runs code
- scripts/bash/pdr-lib.sh 18 KB runs code
- scripts/bash/setup-product-implement.sh 1.2 KB runs code
- scripts/bash/validate-pdr.sh 1.4 KB runs code
- scripts/bash/validate-prd.sh 14 KB runs code
- scripts/powershell/pdr-lib.ps1 11 KB runs code
- scripts/powershell/setup-product-implement.ps1 1.3 KB runs code
- templates/pdr-template.md 2.0 KB
- templates/sections/executive-summary.md 2.4 KB
- templates/sections/goals.md 1.0 KB
- templates/sections/gtm.md 3.2 KB
- templates/sections/investment.md 2.7 KB
- templates/sections/market-opportunity.md 3.0 KB
- templates/sections/metrics.md 1.6 KB
- templates/sections/nfrs.md 1.9 KB
- templates/sections/out-of-scope.md 1.5 KB
- templates/sections/overview.md 4.1 KB
- templates/sections/pdr-summary.md 2.1 KB
- templates/sections/personas.md 2.1 KB
- templates/sections/problem.md 1.0 KB
- templates/sections/requirements.md 5.4 KB
- templates/sections/risks.md 2.4 KB
- templates/sections/roadmap.md 3.4 KB
- templates/subagents/discovery-prompt.md 3.2 KB
- templates/subagents/pattern-prompt.md 4.0 KB
- templates/subagents/synthesis-prompt.md 5.7 KB
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.
- 3d ago Changed · +11 lines 84c3385922e4
- 9d ago First seen · 420 lines · 60 tokens per session scan A 99f36e9b1c95
product-implement is a skill published in the GitHub repository tikalk/adlc-team-skills (133 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 3,916 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-30.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…