Codebase to PRD
Reverse-engineer an existing codebase into a structured PRD so undocumented behavior becomes a readable spec.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a good idea to document your CLI in a PRD format. You should start by describing what the CLI does and who it's for. Then list out the main commands and features. You might want to include some examples of how users would interact with it. It's helpful to explain the design decisions behind why certain features were included. You could also mention any limitations or known issues. A PRD usually includes success metrics so you know if the feature is working well. You might want to include a roadmap of future features. It's useful to have a clear structure so it's easy to skim. Would you like help organizing any particular section?
PRD: AGENTCLI PURPOSE CLI tool enabling agents to execute internal tasks: database queries, credential rotation, report generation. Target: Site Reliability Engineers and Platform Engineers. Success metric: 90% of routine ops tasks automatable via agentcli within 2 months. CORE COMMANDS agentcli db query 'SELECT * FROM users' → CSV or JSON output agentcli secrets rotate cert_name → trigger rotation, verify health agentcli report generate daily → run scheduled reports, output to Cloud Storage agentcli task enqueue job_name --priority high → queue background job DESIGN DECISIONS Why no interactive mode: Agents need fully scripted, reproducible flows. Why Cloud Storage output: Reports live in single source of truth; agents reference by URL. Why rate limits: Prevent cascading failures if agent loops poorly. SUCCESS CRITERIA Adoption: 70%+ of ops runbooks migrated by end Q4 Performance: Average latency under 500ms Reliability: 99.9% uptime, zero security incidents LIMITATIONS No local state: CLI stateless, agent must track IDs No dashboard: Job history requires log queries Rollback story TBD: Long-running jobs cannot reverse in-place ROADMAP Q3 2026: MVP (query, rotate, report, enqueue) Q4 2026: Audit log and approval workflows Q1 2027: Interactive mode for human operators
About this skill
name: cmd-code-to-prd description: Use when Structured Claude skill that gives Claude a repeatable workflow for cmd code to prd.
Cmd Code To Prd
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Cmd Code To Prd workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cmd-code-to-prd skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cmd Code To Prd; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cmd-code-to-prd
description: Use this skill when an existing codebase needs to be reverse-engineered into a structured product requirements document.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Cmd Code To Prd
Gives a repeatable workflow for reverse-engineering an existing codebase into a structured PRD, so undocumented product behavior becomes a readable spec.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.