v1-io/v1-prd
plugins/v1tamins/skills/v1-prd/SKILL.md
Use when writing a PRD from a Linear ticket or feature request. Triggers on "write PRD", "create requirements doc", "PRD from ticket".
$ install --global
skillsauthnpx skillsauth add v1-io/v1tamins v1-prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 2:13 AM154.8s2 files scanned
SKILL.md
- name:
- v1-prd
- description:
- Use when writing a PRD from a Linear ticket or feature request. Triggers on "write PRD", "create requirements doc", "PRD from ticket".
PRD from Linear Ticket
Write a concise, implementation-ready PRD from a Linear ticket or project.
Usage
Typical invocations:
- Claude Code:
/v1-prd <LINEAR_TICKET_ID> - Codex: invoke
v1-prdfrom the skills menu or use$v1-prd <LINEAR_TICKET_ID>
Examples:
/v1-prd ABC-123
/v1-prd https://linear.app/your-team/issue/ABC-123
In Codex, the slash examples below map directly to $v1-prd ....
What It Does
1. Gather Inputs
- Fetches ticket/project from Linear (title, description, acceptance criteria)
- Retrieves linked designs, mocks, or prior context
- If image URLs exist without captions, adds descriptive captions
- Asks for missing inputs if needed
2. Analyze Ticket
- Reads the ticket title and description (may be high-level)
- Examines codebase for existing relevant code and features
- Understands technical context and constraints
3. Write PRD
Creates a Product Requirements Document with these sections:
# [Title]
## Description
[Clear summary of what we're building and why]
## Features
- Feature 1
- Feature 2
## Acceptance Criteria
- [ ] Testable criterion 1
- [ ] Testable criterion 2
## Technical Requirements
- Backend: [specifics]
- Frontend: [specifics]
- Database: [specifics]
## UI/UX Requirements
- [Design specifications]
- [User flows]
## Dependencies
- [External dependencies]
- [Internal dependencies]
## Risks
- [Technical risks]
- [Timeline risks]
## References
[Images with captions if applicable]
4. Upload PRD
- Replaces existing description in the Linear ticket with the PRD
- Adds comment: "PRD uploaded"
PRD Quality Standards
- Readable: Scannable, no fluff
- Testable: Acceptance criteria are verifiable
- Complete: Covers edge cases and error conditions
- Actionable: Technical requirements are specific
- Handoff-ready: Developer can start work immediately
Notes
- Requires Linear access (via whatever Linear tooling the project has wired up)
- Converts ambiguous language into testable statements
- Prefers bullets over prose
- Includes existing images with descriptive captions
Related Skills
v1-io/v1-deep-review
development
VerifiedTrustedCommunity
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for large prs, new features/architectures, a deep code quality audit, or especially harsh maintainability review.
5SKILL.mdUpdated May 23, 2026
v1-io/v1-land-pr
testing
VerifiedTrustedCommunity
Commit, push, open, and land a pull request through CI handoff. Use when work is complete and the user wants an agent to create or update a PR, open it as a draft, monitor GitHub checks with `gh pr checks`, fix failed checks, retry up to three remediation pushes, mark the PR ready for review once green, and move a linked Linear ticket to Human Review when one exists. Trigger on requests like 'land this PR', 'open and monitor a PR', 'commit push and watch CI', 'get this ready for review', or 'finish the PR workflow'.
5SKILL.mdUpdated May 2, 2026
v1-io/v1-code-review
development
VerifiedTrustedCommunity
Use when reviewing a PR, reviewing the current branch, or posting code review feedback to GitHub. Triggers on "review this PR", "code review", "check this pull request", "review my branch", "review and fix".
5SKILL.mdUpdated May 2, 2026
v1-io/v1-bare-bones
development
VerifiedTrustedCommunity
Use when a plan, PRD, proposal, or implementation outline is overscoped, too ambitious for the immediate goal, or needs to be reduced to a bare-bones version. Triggers on "bare bones", "no damn whistles", "no bells and whistles", "strip this plan", "trim this plan", "scope creep", "descope this plan", "MVP only".
4SKILL.mdUpdated May 21, 2026