
using-personal-skills
by solstice035
SKILL.md
name: using-personal-skills description: "Entry point for the personal development workflow. Guides you through the complete planning and execution cycle."
Using Personal Skills
This plugin provides a structured workflow for personal and MVP development, integrating with superpowers skills and PAL tools.
Quick Start
Starting a New Feature
-
Brainstorm the idea:
superpowers:brainstorming -
Define requirements (WHAT/WHY):
personal:prd -
Define architecture (HOW):
personal:trd -
For complex projects, validate design:
mcp__pal__consensus -
Break into tasks:
superpowers:writing-plans -
Execute with TDD:
superpowers:test-driven-development superpowers:executing-plans mcp__pal__precommit git commit -
Complete and merge:
superpowers:verification-before-completion mcp__pal__codereview [Playwright E2E if frontend] User acceptance review Git PR
Available Skills
| Skill | Purpose | When to Use |
|---|---|---|
personal:prd | Product Requirements Document | After brainstorming, before technical design |
personal:trd | Technical Requirements Document | After PRD, before implementation planning |
personal:using-personal-skills | This guide | When you need workflow help |
Complete Workflow
See WORKFLOW.md for the detailed workflow diagram.
Planning Phase
1. superpowers:brainstorming → Explore the idea
2. personal:prd → Define WHAT and WHY
3. personal:trd → Define HOW
4. mcp__pal__consensus → Validate design (complex only)
5. superpowers:writing-plans → Break into tasks
Execution Loop (repeat for each task)
6a. superpowers:test-driven-development → Write failing test
6b. superpowers:executing-plans → Implement to pass
[bug?] → superpowers:systematic-debugging
7. mcp__pal__precommit → Validate changes
8. Git commit → Save progress
Completion Phase
9. superpowers:verification-before-completion → Confirm tests pass
10. mcp__pal__codereview → Final review
11. Playwright E2E → Frontend testing
12. User Acceptance Review → Human validation
13. superpowers:finishing-a-development-branch → Merge strategy
14. Git PR → Merge to dev/main
15. Deploy → Production
Complexity Modes
Simple Projects (< 1 day)
- Quick PRD (problem + stories + scope)
- Simple TRD (architecture + decisions + risks)
- Skip PAL consensus
- Direct to writing-plans
Complex Projects (> 1 day)
- Full PRD with journeys and detailed stories
- Full TRD with data models, APIs, and interactions
- PAL consensus for design validation
- Complete workflow
Integration Points
This workflow integrates with:
| Tool | Purpose |
|---|---|
superpowers:brainstorming | Socratic idea exploration |
superpowers:writing-plans | Task breakdown |
superpowers:test-driven-development | TDD enforcement |
superpowers:executing-plans | Guided implementation |
superpowers:systematic-debugging | Structured debugging |
superpowers:verification-before-completion | Pre-merge validation |
superpowers:finishing-a-development-branch | Merge strategy |
mcp__pal__consensus | Multi-model design review |
mcp__pal__precommit | Pre-commit validation |
mcp__pal__codereview | Final code review |
Playwright | E2E testing for frontend |
File Locations
| Document | Location |
|---|---|
| PRD | docs/plans/YYYY-MM-DD-<feature>-prd.md |
| TRD | docs/plans/YYYY-MM-DD-<feature>-trd.md |
| Workflow Reference | WORKFLOW.md in this plugin |
Tips
-
Don't skip brainstorming - Even for "obvious" features, 10 minutes of Socratic questioning prevents scope creep
-
Be ruthless with MVP scope - If it can wait, put it in v2
-
TDD saves time - Writing tests first catches design issues early
-
Pre-commit every time - Small validated commits are easier to review and revert
-
Use complexity mode wisely - Simple mode for < 1 day tasks, complex mode for everything else
-
PAL consensus for architecture - Multi-model validation catches blind spots in technical design
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon