Agent Skill
2/7/2026

using-personal-skills

Entry point for the personal development workflow. Guides you through the complete planning and execution cycle.

S
solstice035
0GitHub Stars
1Views
npx skills add solstice035/personal-skills

SKILL.md

Nameusing-personal-skills
DescriptionEntry point for the personal development workflow. Guides you through the complete planning and execution cycle.

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

  1. Brainstorm the idea:

    superpowers:brainstorming
    
  2. Define requirements (WHAT/WHY):

    personal:prd
    
  3. Define architecture (HOW):

    personal:trd
    
  4. For complex projects, validate design:

    mcp__pal__consensus
    
  5. Break into tasks:

    superpowers:writing-plans
    
  6. Execute with TDD:

    superpowers:test-driven-development
    superpowers:executing-plans
    mcp__pal__precommit
    git commit
    
  7. Complete and merge:

    superpowers:verification-before-completion
    mcp__pal__codereview
    [Playwright E2E if frontend]
    User acceptance review
    Git PR
    

Available Skills

SkillPurposeWhen to Use
personal:prdProduct Requirements DocumentAfter brainstorming, before technical design
personal:trdTechnical Requirements DocumentAfter PRD, before implementation planning
personal:using-personal-skillsThis guideWhen 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:

ToolPurpose
superpowers:brainstormingSocratic idea exploration
superpowers:writing-plansTask breakdown
superpowers:test-driven-developmentTDD enforcement
superpowers:executing-plansGuided implementation
superpowers:systematic-debuggingStructured debugging
superpowers:verification-before-completionPre-merge validation
superpowers:finishing-a-development-branchMerge strategy
mcp__pal__consensusMulti-model design review
mcp__pal__precommitPre-commit validation
mcp__pal__codereviewFinal code review
PlaywrightE2E testing for frontend

File Locations

DocumentLocation
PRDdocs/plans/YYYY-MM-DD-<feature>-prd.md
TRDdocs/plans/YYYY-MM-DD-<feature>-trd.md
Workflow ReferenceWORKFLOW.md in this plugin

Tips

  1. Don't skip brainstorming - Even for "obvious" features, 10 minutes of Socratic questioning prevents scope creep

  2. Be ruthless with MVP scope - If it can wait, put it in v2

  3. TDD saves time - Writing tests first catches design issues early

  4. Pre-commit every time - Small validated commits are easier to review and revert

  5. Use complexity mode wisely - Simple mode for < 1 day tasks, complex mode for everything else

  6. PAL consensus for architecture - Multi-model validation catches blind spots in technical design

Skills Info
Original Name:using-personal-skillsAuthor:solstice035