CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
A skill your agent uses when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
Install Product Analyze
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tikalk/adlc-team-skills product-analyze --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-analyze .claude/skills/product-analyze && rm -rf skills-srcUse ~/.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/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .claude/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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 install https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyzeType 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.
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tikalk/adlc-team-skills product-analyze --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-analyze .agents/skills/product-analyze && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .agents/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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.
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tikalk/adlc-team-skills product-analyze --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-analyze .cursor/skills/product-analyze && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .cursor/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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 https://github.com/tikalk/adlc-team-skills.git --path skills/product/product-analyze--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tikalk/adlc-team-skills product-analyze --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-analyze .gemini/skills/product-analyze && rm -rf skills-srcUse ~/.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/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .gemini/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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.
$ gh skill install tikalk/adlc-team-skills product-analyzeInstalls 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).
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ 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-analyze .github/skills/product-analyze && rm -rf skills-srcUse ~/.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/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .github/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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.
$ npx skills add tikalk/adlc-team-skills --skill product-analyze -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tikalk/adlc-team-skills product-analyze --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ 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-analyze .opencode/skills/product-analyze && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "product-analyze" agent skill from https://github.com/tikalk/adlc-team-skills/tree/main/skills/product/product-analyze into .opencode/skills/product-analyze/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-analyze", 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-analyze- GitHub stars
- 141
- Token cost
- ~1.7k tokens
- SKILL.md length
- 515 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
- Works in 8 steps: Load Artifacts → PDR Quality Analysis → Inter-PDR Consistency → …
- Checking PDR↔PRD consistency after /product-implement
- SKILL.md covers What this skill does, When to use, When NOT to use and Execution Steps, plus 4 more sections
- Runs Shell and PowerShell scripts from its folder
What it does
Product Analyze is an agent skill from tikalk/adlc-team-skills. Use when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
Its SKILL.md is about 1.7k 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-analyze.sh`).
It sits in Product & Project Management, covering PRD writing. 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
- Checking PDR↔PRD consistency after /product-implement
- Periodically to detect drift
- PDR quality issues
- Cross-PDR conflicts
Example prompts
- “/product-analyze”
Requirements
- A Bash shell
- PowerShell
Workflow steps
8 steps, taken from the step headings in SKILL.md.
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 Analyze loads about 1.7k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 515 words of instructions outside code blocks.
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). 515 words, ~1,731 tokens.
Download SKILL.mdSave it as
.claude/skills/product-analyze/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- product-analyze
- description
- Use when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
- disable-model-invocation
- true
product-analyze
What this skill does
Performs read-only product consistency analysis:
- PDR Quality — completeness, clarity, standards compliance
- PDR→PRD Drift — decisions not reflected in PRD
- PRD→PDR Drift — PRD elements without supporting PDRs
- Cross-PDR Consistency — conflicts between PDRs
- Staleness — outdated references, placeholders, deprecated PDRs still referenced
Output: Structured markdown analysis report (no files modified)
When to use
- After
/product-implementto validate generated PRD - After
/product-clarifyto verify refinements - Before feature development to ensure product is solid
- Periodically to detect drift as product evolves
When NOT to use
- No product artifacts exist (use
/product-initor/product-specifyfirst) - You want to modify files (this is analysis-only)
Execution Steps
Phase 1: Load Artifacts
sh: scripts/bash/setup-product-analyze.sh [--json]
ps: scripts/powershell/setup-product-analyze.ps1Read:
docs/adlc/product/PRD.md(legacy repo-rootPRD.mdfallback — ADR-401 dual-read){REPO_ROOT}/.adlc/drafts/pdr/PDR-*.md(individual PDR files){REPO_ROOT}/docs/adlc/memory/constitution.md, falling back to legacy{REPO_ROOT}/.adlc/memory/constitution.md(ADR-401 dual-read; if either exists)
Build inventory:
| Artifact | Path | Status |
|----------|------|--------|
| Product PRD | docs/adlc/product/PRD.md (legacy PRD.md fallback) | Found/Missing |
| Product PDRs | .adlc/drafts/pdr/ | [N] files |
| Constitution | docs/adlc/memory/constitution.md (legacy .adlc/memory fallback) | Found/Missing |Phase 2: PDR Quality Analysis
For each PDR file, check:
| Dimension | Check | Severity |
|---|---|---|
| Context | Problem clearly stated | MEDIUM |
| Decision | Actionable, testable | HIGH |
| Consequences | Positive AND negative | HIGH |
| Success Metrics | Defined with targets | HIGH |
| Alternatives | At least 2 with neutral trade-offs | HIGH |
| Constitution | Aligns with vision | CRITICAL |
Phase 3: Inter-PDR Consistency
- Conflicting Decisions: PDRs that contradict (e.g., B2B vs B2C)
- Missing Dependencies: PDRs that should reference each other
- Terminology Drift: Same concept named differently
- Strategy Coherence: Problem/persona/metric alignment
Phase 4: PDR→PRD Drift (Forward Sync)
For each PDR, check if decision appears in PRD:
| PDR Element | Expected in PRD | Section |
|---|---|---|
| Problem decision | Problem statement | 3 |
| Persona decision | Personas | 6 |
| Scope decision | Requirements / Out of Scope | 7 / 9 |
| Metric decision | Success Metrics | 5 |
| Business Model | Overview | 2 |
| NFR decision | Non-Functional Requirements | 8 |
Phase 5: PRD→PDR Drift (Backward Sync)
- Requirements Without PDRs: User stories without scope justification
- Personas Without PDRs: Personas with no persona PDR
- Metrics Without PDRs: Success metrics with no metric PDR
- Risks Without PDRs: Risks without consequence documentation
Show full SKILL.md (203 more words)Show less
Phase 6: Staleness Detection
- Deprecated PDRs Still Referenced: PRD references status "Deprecated"
- Placeholders:
[TODO],[TBD],[PRODUCT_NAME],[DATE] - Date Inconsistencies: PDR dates older than PRD last-updated
- Orphaned References: PDR IDs mentioned but file doesn't exist
Phase 7: Severity Assignment
| Severity | Criteria |
|---|---|
| CRITICAL | Constitution violation, major requirement undocumented |
| HIGH | PDR→PRD drift affecting requirements, conflicting PDRs |
| MEDIUM | Incomplete consequences, staleness, terminology drift |
| LOW | Style improvements, minor documentation gaps |
Phase 8: Generate Report
## Product Analysis Report
### Analysis Summary
| Attribute | Value |
|-----------|-------|
| Mode | [Full/PDRs/Sections] |
| Files Analyzed | [List] |
| Analysis Date | [Current date] |
### Findings
| ID | Pass | Severity | Location | Summary | Recommendation |
|----|------|----------|----------|---------|----------------|
| A1 | PDR Quality | MEDIUM | PDR-003 | Missing success metrics | Add metrics section |
| B1 | Inter-PDR | HIGH | PDR-002, PDR-005 | Conflicting target markets | Resolve B2B vs B2C |
| C1 | PDR→PRD | HIGH | PRD:5 | Persona not in PRD | Update PRD section 5 |
| D1 | PRD→PDR | HIGH | PRD:6 | Feature has no PDR | Create PDR |
| F1 | Staleness | LOW | PRD:1 | [PRODUCT_NAME] placeholder | Fill product name |
### Coverage Metrics
| Metric | Value |
|--------|-------|
| PDR Count | [N] |
| PRD Sections Complete | [N]/12 |
| PDR→PRD Coverage | [N]% |
| PRD→PDR Coverage | [N]% |
### Issue Distribution
| Severity | Count |
|----------|-------|
| CRITICAL | [N] |
| HIGH | [N] |
| MEDIUM | [N] |
| LOW | [N] |
### Next Actions
- **CRITICAL issues**: Resolve constitution violations before proceeding
- Command: `/product-clarify`
- **HIGH PDR quality**: Address missing alternatives and consequences
- Command: `/product-clarify`
- **PDR→PRD drift**: Update PRD to reflect PDR decisions
- Command: `/product-implement --update`
- **PRD→PDR drift**: Create missing PDRs
- Command: `/product-specify` or `/product-init`Key Rules
Analysis Integrity
- NEVER modify files — this is read-only
- NEVER hallucinate missing content — report absences accurately
- Prioritize constitution violations — always CRITICAL
- Use evidence-based findings — cite specific locations
Reporting Standards
- Limit to 50 findings — aggregate overflow in summary
- Include location — always cite file or section
- Provide actionable recommendations — each finding gets a fix suggestion
- Calculate coverage metrics — quantify completeness
Configuration
PDR_DRAFTS_DIR—{REPO_ROOT}/.adlc/drafts/pdrPRD_FILE—{REPO_ROOT}/docs/adlc/product/PRD.mdCONSTITUTION—{REPO_ROOT}/docs/adlc/memory/constitution.md(legacy.adlc/memory/constitution.mdfallback)
12-Factor Alignment
- Factor IX (Verification-First): Validates artifacts before downstream work
- Factor XI (Directives as Code): Checks version-controlled directive quality
Verification
- All artifacts loaded and inventoried
- PDR quality checklist applied to each file
- Cross-PDR consistency verified
- Bidirectional drift detection completed
- Staleness scan performed
- Severities assigned correctly
- Report structured with findings table
- Coverage metrics calculated
- Next actions recommended with commands
- Zero files modified
© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in skills/product/product-analyze of tikalk/adlc-team-skills.
- SKILL.md
- scripts/bash/setup-product-analyze.sh
- scripts/powershell/setup-product-analyze.ps1
Open the folder on GitHubat commit 2dbed36
Compare with similar skills
Product Analyze 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Analyze this skilltikalk/adlc-team-skills | 141 | — | ~1.7k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Trellis Brainstormanjiemo/SunnyBeach | 178 | 7 repos | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Adversarial Speczscole/adversarial-spec | 556 | 1 repos | ~8.3k | Automated safety check: Notes | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
Adversarial Spec
zscole/adversarial-spec
Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
More from tikalk/adlc-team-skills
All 44 skills in this repoWorkspace
tikalk/adlc-team-skills
A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…
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…
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.
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…
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.
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.
Related
Categories
Questions about Product Analyze
What does Product Analyze do?
A skill your agent uses when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness. Product Analyze is an agent skill from tikalk/adlc-team-skills. Use when checking PDR↔PRD consistency after /product-implement or periodically to detect drift, PDR quality issues, cross-PDR conflicts, and staleness.
When should I use Product Analyze?
Product Analyze fits situations like: checking PDR↔PRD consistency after /product-implement; periodically to detect drift; PDR quality issues; cross-PDR conflicts.
How do I install Product Analyze in Claude Code?
Run `npx skills add tikalk/adlc-team-skills --skill product-analyze -a claude-code`. Or copy the skill folder (skills/product/product-analyze in tikalk/adlc-team-skills) into .claude/skills/product-analyze in your project. Claude Code loads it when a task matches its description.
How do I install Product Analyze in Codex?
Run `npx skills add tikalk/adlc-team-skills --skill product-analyze -a codex`. Or copy the skill folder (skills/product/product-analyze in tikalk/adlc-team-skills) into .agents/skills/product-analyze in your project. Codex loads it when a task matches its description.
Can I use Product Analyze 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-analyze -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-analyze, .gemini/skills/product-analyze, .github/skills/product-analyze and .opencode/skills/product-analyze in your project.
What does Product Analyze need to run?
Going by SKILL.md and its folder, Product Analyze needs a shell and PowerShell for the scripts in its folder. Our summary lists: A Bash shell; PowerShell.
Does Product Analyze 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 Analyze 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 Analyze use?
Product Analyze 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 Analyze use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Analyze?
Skills that share tags, products or a category with Product Analyze: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Adversarial Spec (zscole/adversarial-spec, 556 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Analyze?
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.