alfredolopez80/plan
.claude/skills/plan/SKILL.md
Plan-State Management for Ralph. Create, track, and manage implementation plans with LSA verification. Coordinates with 6 ralph-* teammates including ralph-frontend and ralph-security.
$ install --global
skillsauthnpx skillsauth add alfredolopez80/multi-agent-ralph-loop planInstall 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: Apr 15, 2026, 6:06 PM8.0s1 file scanned
SKILL.md
- # VERSION:
- 3.0.0
- name:
- plan
- description:
- Plan-State Management for Ralph. Create, track, and manage implementation plans with LSA verification. Coordinates with 6 ralph-* teammates including ralph-frontend and ralph-security.
- user-invocable:
- true
v2.88 Key Changes (MODEL-AGNOSTIC)
- Model-agnostic: Uses model configured in
~/.claude/settings.jsonor CLI/env vars - No flags required: Works with the configured default model
- Flexible: Works with GLM-5, Claude, Minimax, or any configured model
- Settings-driven: Model selection via
ANTHROPIC_DEFAULT_*_MODELenv vars
Plan-State Management
Create, track, and manage implementation plans with Lead Software Architect verification.
Subcommands
init - Initialize new plan
/plan init "Implement user authentication"
Creates .claude/plan-state.json with:
- Task title, phases, risk level
- File modifications list
- Test strategy
- Validation criteria
status - Show plan status
/plan status
Displays:
- Current phase
- Completed vs pending steps
- Overall progress percentage
- Next action required
add-step - Add implementation step
/plan add-step "Create User model with validation"
Appends step to phases array with:
- Step description
- Assigned agent/model
- Dependencies
- Validation criteria
start - Begin implementation
/plan start
Triggers:
- LSA pre-verification
- Plan-Sync monitoring activation
- First phase execution
complete - Mark step complete
/plan complete --step 2
Updates plan-state.json and logs completion in ledger.
verify - Verify plan completion
/plan verify
Runs full validation against requirements:
- LSA architecture check
- Quality gate verification
- Requirements coverage
sync - Synchronize with execution
/plan sync
Detects drift between plan and execution, patches downstream references.
Workflow
/plan init "Feature description"
↓ (creates plan-state.json)
/plan add-step "Step 1"
/plan add-step "Step 2"
↓
/plan start
↓ (LSA verification)
/plan complete --step 1
/plan complete --step 2
↓
/plan verify
↓
VERIFIED_DONE
Output Examples
Plan Status Output
========================================
PLAN STATE: Feature Implementation
========================================
Status: In Progress
Phase: 2/4 - Backend Implementation
Progress: 45%
Steps:
✅ 1. Database Schema - COMPLETE
⏳ 2. API Endpoints - IN PROGRESS
🔲 3. Frontend Integration
🔲 4. Testing & Validation
Next Action: /plan complete --step 2
========================================
Related Skills
/orchestrator- Full orchestration with plan integration/iterate- Iterative execution following plan steps/gates- Quality validation at plan milestones/retrospective- Post-completion analysis
Related Skills
alfredolopez80/vault
development
VerifiedTrustedCommunity
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/spec
testing
VerifiedTrustedCommunity
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/ship
testing
VerifiedTrustedCommunity
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
121SKILL.mdUpdated Apr 15, 2026
alfredolopez80/perf
development
VerifiedTrustedCommunity
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
121SKILL.mdUpdated Apr 15, 2026