product-implement

product-implement is a skill for Claude Code from tikalk/adlc-team-skills. It costs 21 tokens per session (3,958 once invoked), scanned A, original, MIT.

A workflow that turns approved Product Decision Records, or PDRs, into a complete Product Requirements Document, or PRD. A PRD is a document describing what a product or feature should do and how it should be validated.

In plain words
What is it for?
Use it after product decisions have been approved, or when documenting an existing product, to create PRD sections, validate them, and organize the source records.
Why use it?
It organizes requirements from several decisions into one consistent document and checks that the required input exists before starting.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Use it after product decisions have been approved, or when documenting an existing product, to create PRD sections, validate them, and organize the source records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tikalk/adlc-team-skills/product-implement
Install

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.

Any agent
npx skills add tikalk/adlc-team-skills --skill product-implement
Clone the repo
git clone --depth 1 https://github.com/tikalk/adlc-team-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for product-implement

README.md
[![agentmods](https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/product-implement/github.svg)](https://agentmods.dev/skills/tikalk/adlc-team-skills/product-implement)
Your own site
<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.

agentmods 80×15 button for product-implement

Your own site · 80×15
<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>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,958 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.03958
Opus 5.5 $0.00008 $0.01583
Sonnet 5.5 $0.00004 $0.00792
Haiku 4.5 $0.00002 $0.00396

Measured 5d ago against content hash 217b38c41dc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 5d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/bash/migrate-pdr-frontmatter.sh, scripts/bash/setup-product-implement.sh, scripts/bash/validate-pdr.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/product/product-implement/SKILL.md · 433 lines

How it starts

The opening of the file, as written. The whole thing — 433 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:

  1. Plan Agent: Analyze PDRs, detect feature-areas, generate customized DAG, get user approval
  2. Execute Agent: Generate sections per feature-area with mandatory checkpoint after Requirements
  3. Summarize Agent: Aggregate sections, resolve conflicts, produce unified PRD.md

Output:

  • docs/adlc/product/PRD.md — self-contained product requirements (the shared layout; legacy repo-root PRD.md stays read-compatible)
  • {REPO_ROOT}/.adlc/product/sections/{feature-area}/{section}.md — intermediate section files
  • Accepted PDRs moved to {REPO_ROOT}/docs/adlc/memory/pdr/ (the shared layout canonical memory root)

When to use

  • After /product-clarify has approved PDRs
  • After /product-init to document existing product
  • PDR updates requiring PRD regeneration

When NOT to use

  • No Accepted PDRs (run /product-clarify first)
  • Minor PRD edits (edit PRD.md directly)

Pre-Flight Validation

Before starting, verify prerequisites:

  1. Check PDRs exist: {REPO_ROOT}/.adlc/drafts/pdr/PDR-*.md
  2. 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

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     │
└─────────────────────────────────────────────────────────┘

Read the full file on GitHub · 433 lines

Changes

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.

  1. 5d ago Changed 217b38c41dc8
  2. 25d ago Changed 6e5fd7c837dd
  3. 26d ago Changed · +2 lines 40dd6910bdba
  4. 1mo ago Changed 2de0bf1b66e2
  5. 1mo ago Changed · -39 tokens per session cb2ead7ba554
  6. 1mo ago Changed · +11 lines 84c3385922e4
  7. 1mo ago First seen · 420 lines · 60 tokens per session scan A 99f36e9b1c95

Subscribe to this mod's changes

product-implement is a skill published in the GitHub repository tikalk/adlc-team-skills (143 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 3,958 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-08-30.

Related

Other skills, from other repositories

building-agents

Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…

ericrisco/rsc-harness · 85 tokens

agent-eval

Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…

ericrisco/rsc-harness · 79 tokens

decision-records

Use when a hard-to-reverse choice (database, framework, vendor, auth model) must be frozen as an immutable numbered ADR — the context that forced it, the options weighed, the decision, consequences both ways — or superseded without erasing history. NOT a meeting recap (that is meeting-notes), NOT standing project…

ericrisco/rsc-harness · 76 tokens

prompt-engineering

Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…

ericrisco/rsc-harness · 83 tokens

respect-the-oracle

Use when working against a test suite, spec, or graded harness you do not own - especially inside an automated loop scored on how many tests pass - and tempted to change the tests, weaken assertions, hardcode expected outputs, special-case inputs, or overfit the visible examples to turn things green.

chris-short/respect-the-oracle · 65 tokens

refocusing

Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.

mvschwarz/openrig · 59 tokens