Agent skill

Product Init

A skill your agent uses when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.

MITAuto-check passedAgent Workflows

Install Product Init

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product/product-init .claude/skills/product-init && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .claude/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/product/product-init .agents/skills/product-init && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .agents/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/product/product-init .cursor/skills/product-init && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .cursor/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tikalk/adlc-team-skills.git --path skills/product/product-init

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/product/product-init .gemini/skills/product-init && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .gemini/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/product/product-init .github/skills/product-init && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .github/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tikalk/adlc-team-skills --skill product-init -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tikalk/adlc-team-skills product-init --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/product/product-init .opencode/skills/product-init && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "product-init" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-init into .opencode/skills/product-init/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-init", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: product-init
GitHub stars: 141
Token cost: ~2.3k tokens
SKILL.md length: 585 words
Files: 3 (incl. scripts)
Skills in repo: 44
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.

Works in 8 steps: Environment Setup → Feature-Area Detection → Discovery Agent (Per Feature-Area) → …
Documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis
SKILL.md covers What this skill does, When to use, When NOT to use and Execution Steps, plus 7 more sections
Runs Shell and PowerShell scripts from its folder

What it does

Product Init is an agent skill from tikalk/adlc-team-skills. Use when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/bash/setup-product-init.sh`).

It sits in Agent Workflows. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.

When your agent uses it

Documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis

Example prompts

“/product-init”

Requirements

A Bash shell
PowerShell

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Environment Setup
Feature-Area Detection
Discovery Agent (Per Feature-Area)
Pattern Agent (Per Feature-Area)
Synthesis Agent (Cross-Feature-Area)
Write Individual PDR Files
Regenerate PDR Index
Output Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 2dbed36. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell and PowerShell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Init loads about 2.3k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 585 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~36
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from tikalk/adlc-team-skills at commit 2dbed36, republished under its MIT licence (© tikalk). 585 words, ~2,338 tokens.

Download SKILL.mdSave it as .claude/skills/product-init/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: product-init
description: Use when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.
disable-model-invocation: true

product-init

What this skill does

Reverse-engineers product decisions from an existing product using a three-phase analysis pipeline:

Discovery Agent: Scans each feature-area for raw product signals (code, docs, pricing)
Pattern Agent: Classifies signals into PDR categories, scores strategic importance
Synthesis Agent: Cross-feature-area analysis, flags inconsistencies

Output: Individual PDR-{NNN}.md files (status Discovered) in .adlc/drafts/pdr/ with an auto-generated pdr.md index.

When to use

Existing product with no formal PDRs
Brownfield codebase needs product documentation
Team onboarding — walking through product rationale
Post-acquisition or inherited codebase

When NOT to use

New product (use /product-specify instead)
Minor PDR updates (use /product-clarify instead)

Execution Steps

Phase 0: Environment Setup

Run setup script to resolve paths and detect feature-areas:

bash

sh: scripts/bash/setup-product-init.sh [--json]
ps: scripts/powershell/setup-product-init.ps1

Requires: the product-clarify skill (provides pdr-lib.sh): adlc-cli skills add tikalk/adlc-team-skills --skill product-clarify

Setup output (JSON):

json

{
  "REPO_ROOT": "/path/to/project",
  "PDR_DRAFTS_DIR": "/path/to/project/.adlc/drafts/pdr",
  "PRD_FILE": "/path/to/project/PRD.md",
  "feature_areas": ["core", "business", "growth"],
  "next_pdr": "001"
}

Create directories:

bash

mkdir -p "{REPO_ROOT}/.adlc/drafts/pdr"
mkdir -p "{REPO_ROOT}/.adlc/product"

Phase 1: Feature-Area Detection

Detect feature-areas from three sources:

Source	Detection Pattern
Directory Structure	`src/auth/`, `features/payments/`, `modules/`
Documentation	README sections, existing PRD, ROADMAP
Pricing Tiers	Starter/Pro/Enterprise feature mapping

Present detected areas:

markdown

## Detected Feature-Areas

| # | Feature-Area | Sources | Evidence |
|---|--------------|---------|----------|
| 1 | **Core** | Directory + Docs | src/users/, README "Core Features" |
| 2 | **Business** | Directory + Pricing | src/billing/, pricing.md tiers |

Reply: Y to confirm, n for monolithic, or suggest changes.

Threshold Logic:

≤3 areas: Auto-approve
4-6 areas: Confirm with user
6 areas: Suggest grouping

Phase 2: Discovery Agent (Per Feature-Area)

For each feature-area in order:

Scan directory for monetization signals, user flows, features
Analyze documentation (README, PRD, pricing)
Identify pricing tier mappings
Document evidence

Progress report per area:

Discovery Agent: business feature-area
├── Directory signals: 4
├── Documentation signals: 2
├── Pricing signals: 1
└── Status: ✓ Completed

Phase 3: Pattern Agent (Per Feature-Area)

For each feature-area:

Categorize signals into PDR categories (Problem, Persona, Scope, Metric, etc.)
Score strategic importance (0.0-1.0)
Check for duplicates against existing PDRs
Identify cross-area candidates

Phase 4: Synthesis Agent (Cross-Feature-Area)

1. Cross-Area Pattern Detection:

json

{
  "pattern_id": "P001",
  "pattern_name": "Admin Persona",
  "feature_area_presence": {"core": true, "business": true},
  "is_cross_area": true
}

2. Inconsistency Detection:

Priority conflicts
Duplicate problems
Inconsistent metrics
Generate flags (embedded in affected PDRs)

3. PDR Generation: High-strategic patterns (>0.7) and cross-area patterns (≥2 areas)

Phase 5: Write Individual PDR Files

For each discovered PDR:

Assign ID: PDR-{NNN} using next available number
Write file: {REPO_ROOT}/.adlc/drafts/pdr/PDR-{NNN}.md

PDR file format (individual file, YAML frontmatter — use the shared template):

Use the template at {REPO_ROOT}/.agents/skills/product/../templates/pdr-template.md as the canonical PDR format. The template includes YAML frontmatter (status, date, owner, category, feature-area, title) as the single source of truth for index generation, plus the standard PDR body sections.

markdown

---
status: discovered
date: YYYY-MM-DD
owner: [Inferred from codebase/authors]
category: [Problem | Persona | Scope | Metric | Prioritization | Business Model | Feature | NFR]
feature-area: [core | business | growth | ...]
title: [Decision Title]
---

# PDR-001: [Decision Title]

### Cross-Feature-Area Metadata
- **Appears in**: [business, growth]
- **Cross-area count**: 2
- **Is cross-area pattern**: ✓

### ⚠️ Inconsistency Flags
*None* (or flag details if detected)

### Context
**Problem/Opportunity:**
[Clear description]

**Market Forces:**
- [Market factor 1]
- [Customer feedback]

### Decision
**Decision Statement:**
[Clear statement]

**Rationale:**
[Why this option]

### Consequences
#### Positive
- [Benefit 1]

#### Negative
- [Trade-off 1]

#### Risks
- [Risk with mitigation]

### Success Metrics
| Metric | Target | Measurement Method |
|--------|--------|-------------------|
| [Metric] | [Target] | [Method] |

### Alternatives Considered
#### Option A: [Alternative Name]
**Description:** [Brief description]
**Trade-offs:** [Neutral comparison]

Show full SKILL.md (230 more words)Show less

Phase 6: Regenerate PDR Index

Generate {REPO_ROOT}/.adlc/drafts/pdr/pdr.md from all PDR-*.md files:

bash

# For each PDR-*.md file, extract ID, title, status, date
# Build index table

Index format:

markdown

# Product Decision Records

## PDR Index

| ID | Feature-Area | Category | Status | Date | Owner |
|----|--------------|----------|--------|------|-------|
| PDR-001 | business | Business Model | Discovered | 2026-01-20 | [Inferred] |
| PDR-002 | core | Persona | Discovered | 2026-01-20 | [Inferred] |

---

## Cross-Feature-Area Analysis Summary

### Cross-Area Patterns
| Pattern | Feature-Areas | PDR |
|---------|---------------|-----|
| Admin Persona | core, business | PDR-002 |

### Inconsistencies Flagged
| Flag ID | Type | PDRs Affected | Severity |
|---------|------|---------------|----------|
| FLG-001 | Priority Conflict | PDR-003 | Medium |

---

*Individual PDR files are in this directory (PDR-*.md)*

Phase 7: Output Summary

markdown

## Product Init Complete ✓

### Execution Stats
- **Feature-areas analyzed**: 3
- **Discovery Agent runs**: 3
- **Pattern Agent runs**: 3
- **Synthesis Agent runs**: 1

### PDRs Generated
| Category | Count | Cross-Area |
|----------|-------|------------|
| Business Model | 2 | ✓ |
| Persona | 3 | ✓ |
| Problem | 2 | |
| Prioritization | 1 | |
| **With Inconsistency Flags** | **2** | |

### Next Steps
1. Review PDRs: `{REPO_ROOT}/.adlc/drafts/pdr/`
2. **Resolve inconsistencies**: Run `/product-clarify`
3. Generate PRD: Run `/product-implement`

PDR Numbering Rules

Scan {REPO_ROOT}/.adlc/drafts/pdr/ for existing PDR-*.md files
Extract numeric suffix, find maximum
Next PDR = max + 1, zero-padded to 3 digits (PDR-001, PDR-002, ...)
Never reuse numbers, even for deleted PDRs

State Management

State file: {REPO_ROOT}/.adlc/product/state.json

json

{
  "version": "1.0",
  "command": "product-init",
  "created_at": "2026-01-20T10:00:00Z",
  "phase": "completed",
  "feature_areas": [
    {"id": "core", "name": "Core", "progress": {"discovery": "completed", "pattern": "completed"}}
  ],
  "pdrs_generated": 9,
  "cross_area_patterns": 5,
  "inconsistencies": 2
}

Configuration

PDR_DRAFTS_DIR — {REPO_ROOT}/.adlc/drafts/pdr (individual PDR files)
PDR_INDEX — {REPO_ROOT}/.adlc/drafts/pdr/pdr.md (auto-generated index)
PRD_FILE — {REPO_ROOT}/docs/adlc/product/PRD.md
STATE_FILE — {REPO_ROOT}/.adlc/product/state.json

12-Factor Alignment

Factor III (Mission Definition): Discovers the "what & why" behind existing code
Factor IX (Traceability): Every inferred decision is documented with evidence

Common Rationalizations

Rationalization	Reality
"The code is self-documenting."	Code shows how, not why. PDRs capture rationale that code cannot.
"I'll just read the README."	READMEs describe features, not decisions. PDRs capture the decision tree.
"Brownfield products don't need PDRs."	Every product has implicit decisions. Making them explicit prevents repeated mistakes.

Red Flags

Generating PDRs without codebase evidence — brownfield PDRs must be grounded in actual code/docs, not fabricated rationales.
Skipping inconsistency flags — cross-area conflicts are real signals, not noise.
Assigning "Proposed" status to discovered PDRs — brownfield PDRs are Discovered, not proposed.

Verification

Setup script returns valid JSON with all paths
.adlc/drafts/pdr/ directory exists
At least one PDR-*.md file created with status "Discovered"
pdr.md index auto-generated with correct table
State file written to .adlc/product/state.json
Inconsistency flags embedded in affected PDRs (not separate files)
Cross-feature-area analysis summary in index
No duplicate PDR IDs

Files

SKILL.md and 2 other files (scripts) in skills/product/product-init of tikalk/adlc-team-skills.

SKILL.md
scripts/bash/setup-product-init.sh
scripts/powershell/setup-product-init.ps1

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Product Init next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Init compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Product Init this skilltikalk/adlc-team-skills	141	—	~2.3k	Automated safety check: Pass	MIT	yesterday
Setup Matt Pocock Skillsywwynm/EverythingDone	144	9 repos	~1.7k	Automated safety check: Pass	GPL-3.0	23 days ago
Sagawarpdotdev/common-skills	606	—	~4.1k	Automated safety check: Pass	MIT	7 days ago
PiyazFrkAk/piyaz	194	—	~13k	Automated safety check: Pass	AGPL-3.0	8 days ago
Living Docs Governanceqshanx/docs-governance	130	—	~4.1k	Automated safety check: Pass	MIT	2 days ago
Autodev Paralleljh941213/my-cc-harness	126	—	~1.3k	Automated safety check: Notes	None	2 mo ago

Similar skills

Setup Matt Pocock Skills
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
144 GitHub starsUsed in 9 repos~1.7k tokens
Agent WorkflowsAuto-check passed
Saga
warpdotdev/common-skills
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.
606 GitHub stars~4.1k tokensUpdated 7 days ago
Agent WorkflowsAuto-check passed
Piyaz
FrkAk/piyaz
A skill your agent uses when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work…
194 GitHub stars~13k tokensUpdated 8 days ago
Agent WorkflowsAuto-check passed
Living Docs Governance
qshanx/docs-governance
把长期项目的文档当成一个小系统来维护，防止文档腐烂——四份各司其职的脊柱文件（CLAUDE.md 共享章程 / CLAUDEMAP.md 地图 / PROJECTSTATUS.md 健康仪表盘 / PROJECTLOG.md 流水账）+ Codex 的 AGENTS.md 入口桥接 + 固定读序，并按需连接 ARCHITECTURE、CONTEXT、ADR、契约、测试、回归和 Issue…
130 GitHub stars~4.1k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Autodev Parallel
jh941213/my-cc-harness
Parallel version of the Ralph Loop. An agent skill from jh941213/my-cc-harness.
126 GitHub stars~1.3k tokensUpdated 2 mo ago
Agent WorkflowsAuto-check: notes
Spec
kdlbs/kandev
Create or update Kandev product requirements and system-design documents before implementation.
903 GitHub stars~2.1k tokensUpdated today
Agent WorkflowsAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo

Team Boot
tikalk/adlc-team-skills
A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…
141 GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Architect Clarify
tikalk/adlc-team-skills
A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.
141 GitHub stars~4.7k tokensUpdated yesterday
Auto-check passed
Change Clarify
tikalk/adlc-team-skills
A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…
141 GitHub stars~2.9k tokensUpdated yesterday
Auto-check passed
Change Init
tikalk/adlc-team-skills
A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.
141 GitHub stars~3.5k tokensUpdated yesterday
Auto-check passed
Change Publish
tikalk/adlc-team-skills
A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.
141 GitHub stars~2k tokensUpdated yesterday
Auto-check passed
Evals Analyze
tikalk/adlc-team-skills
A skill your agent uses when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.
141 GitHub stars~1.2k tokensUpdated yesterday
Auto-check passed

Questions about Product Init

What does Product Init do?

A skill your agent uses when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis. Product Init is an agent skill from tikalk/adlc-team-skills. Use when documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.

When should I use Product Init?

Product Init fits situations like: documenting product decisions inferred from an already-built product (brownfield) via multi-agent feature-area analysis.

How do I install Product Init in Claude Code?

Run `npx skills add tikalk/adlc-team-skills --skill product-init -a claude-code`. Or copy the skill folder (skills/product/product-init in tikalk/adlc-team-skills) into .claude/skills/product-init in your project. Claude Code loads it when a task matches its description.

How do I install Product Init in Codex?

Run `npx skills add tikalk/adlc-team-skills --skill product-init -a codex`. Or copy the skill folder (skills/product/product-init in tikalk/adlc-team-skills) into .agents/skills/product-init in your project. Codex loads it when a task matches its description.

Can I use Product Init in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill product-init -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-init, .gemini/skills/product-init, .github/skills/product-init and .opencode/skills/product-init in your project.

What does Product Init need to run?

Going by SKILL.md and its folder, Product Init needs a shell and PowerShell for the scripts in its folder. Our summary lists: A Bash shell; PowerShell.

Does Product Init access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Init safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Product Init use?

Product Init is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Init use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Init?

Skills that share tags, products or a category with Product Init: Setup Matt Pocock Skills (ywwynm/EverythingDone, 144 stars), Saga (warpdotdev/common-skills, 606 stars), Piyaz (FrkAk/piyaz, 194 stars) and Living Docs Governance (qshanx/docs-governance, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Init?

tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Product Init

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

product-init

What this skill does

When to use

When NOT to use

Execution Steps

Phase 0: Environment Setup

Phase 1: Feature-Area Detection

Phase 2: Discovery Agent (Per Feature-Area)

Phase 3: Pattern Agent (Per Feature-Area)

Phase 4: Synthesis Agent (Cross-Feature-Area)

Phase 5: Write Individual PDR Files

Phase 6: Regenerate PDR Index

Phase 7: Output Summary

PDR Numbering Rules

State Management

Configuration

12-Factor Alignment

Common Rationalizations

Red Flags

Verification

Files

Compare with similar skills

Similar skills

More from tikalk/adlc-team-skills

Related

Questions about Product Init