Create Prd
A Claude skill from Karthick-Ramachandran/persist-os.
Install
$ agentstack add skill-karthick-ramachandran-persist-os-create-prd ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-karthick-ramachandran-persist-os-create-prd) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: Create PRD
Purpose
Create a useful feature PRD that helps humans and AI agents understand what should be built and why.
Inputs
- Feature name or problem statement.
- User goal or business reason.
- Any existing product notes, tickets, or change requests.
Required Reading
docs/00-product/BRD.mddocs/00-product/PRD.md- Relevant existing
docs/40-features// - Relevant accepted ADRs in
docs/adrs/
Output Files
docs/40-features//PRD.mddocs/40-features//ACCEPTANCE.md, when acceptance criteria are part of the request.docs/40-features//CHANGE_REQUESTS.md, when changing existing requirements.
Process
- Identify the user, problem, desired outcome, and non-goals.
- Link the feature to product goals and existing source-of-truth docs.
- Define acceptance criteria that can be tested.
- Capture security, privacy, file write, dependency, and MCP implications.
- Identify architecture areas that require follow-up review.
- Keep the PRD concise and implementation-guiding.
Stop Conditions
Stop and request human decision if:
- Product intent is contradictory.
- A requested behavior conflicts with an accepted ADR.
- The feature adds network, telemetry, AI API, cloud, MCP runtime, auth, secrets, or file write
behavior without explicit approval.
- Scope is too broad to define testable acceptance criteria.
Quality Bar
- The PRD states goals, non-goals, users, acceptance criteria, risks, and source links.
- Acceptance criteria are concrete enough to drive tests.
- Security and architecture implications are not generic filler.
- The PRD does not duplicate full architecture docs.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Karthick-Ramachandran
- Source: Karthick-Ramachandran/persist-os
- License: MIT
- Homepage: https://persist-os.pages.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.