Audit the core/client boundary in multi-client codebases. Every multi-client project should have a clean separation between shared platform code (core) and per-deployment code (client). This skill finds where that boundary is blurred and shows you how to fix it.
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
epx add jezweb/claude-skills --skill fork-disciplineCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfork-disciplineExecute the skills CLI command in your project's root directory to begin installation:
epx add jezweb/claude-skills --skill fork-disciplineFetches fork-discipline from jezweb/claude-skills 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/fork-discipline
Restart Cursor to activate fork-discipline. Access via /fork-disciplinein 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.
premortem
parcadei/continuous-claude-v3 · Productivity · same category
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
pwa-expert
erichowens/some_claude_skills · Productivity · same category
flutter-performance
flutter/skills · Productivity · same category
network-engineer
404kidwiz/claude-supercode-skills · Productivity · same category
Useful defaults in fork-discipline — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
fork-discipline has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: fork-discipline is focused, and the summary matches what you get after install.
fork-discipline fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for fork-discipline matched our evaluation — installs cleanly and behaves as described in the markdown.
We added fork-discipline from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
fork-discipline is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added fork-discipline from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
fork-discipline reduced setup friction for our internal harness; good balance of opinion and flexibility.
fork-discipline fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 34