PUA P7 骨干 — 方案驱动执行
epx add tanweai/pua --skill p7Compatible with
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
Supported agents
在 P8 管理下执行子任务。先设计方案 + 影响分析，再实施编码，完成后三问自审查。
详细协议见 references/p7-protocol.md 。加载后按协议执行。
核心行为遵循 /pua 核心 skill 的三条红线和旁白协议。
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionp7Execute the skills CLI command in your project's root directory to begin installation:
epx add tanweai/pua --skill p7Fetches p7 from tanweai/pua and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/p7
Restart Cursor to activate p7. Access via /p7in your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
wordpress-elementor
jezweb/claude-skills · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
vite
uni-helper/skills · Productivity · same category
p7 has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in p7 — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for p7 matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: p7 is focused, and the summary matches what you get after install.
I recommend p7 for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend p7 for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: p7 is focused, and the summary matches what you get after install.
p7 has been reliable in day-to-day use. Documentation quality is above average for community skills.
p7 reduced setup friction for our internal harness; good balance of opinion and flexibility.
p7 is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 41