simplerick0/project-management
skills/project-management/SKILL.md
Project planning, task tracking, and team coordination for software development. Use for sprint planning, backlog grooming, task breakdown, dependency analysis, progress tracking, and stakeholder communication.
development
Updated May 25, 2026
$ install --global
skillsauthnpx skillsauth add simplerick0/com.ackhax.configs project-managementInstall 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: May 25, 2026, 4:35 AM69.4s1 file scanned
SKILL.md
- name:
- project-management
- description:
- Project planning, task tracking, and team coordination for software development. Use for sprint planning, backlog grooming, task breakdown, dependency analysis, progress tracking, and stakeholder communication.
Project Management
Plan, track, and coordinate software development projects effectively.
Task Breakdown
Work Decomposition
- Break features into deliverable units (1-3 day effort)
- Identify dependencies between tasks
- Define clear acceptance criteria
- Estimate complexity (not time)
Task Sizing (Story Points)
| Points | Description | |--------|-------------| | 1 | Trivial change, well-understood | | 2 | Small task, minor complexity | | 3 | Medium task, some unknowns | | 5 | Larger task, multiple components | | 8 | Complex task, significant effort | | 13 | Very complex, consider splitting |
Sprint Planning
Capacity Planning
Available capacity = Team size × Days × Focus factor (0.6-0.8)
Recommended commitment = 70-80% of capacity
Buffer = 20-30% for unknowns
Sprint Structure
- Planning - Select and commit to sprint goals
- Daily sync - Blockers, progress, coordination
- Development - Execute on committed work
- Review - Demo completed work
- Retrospective - Process improvements
Dependency Analysis
Identify Dependencies
- Technical: APIs, data schemas, libraries
- Resource: People, environments, tools
- External: Third-party services, approvals
Critical Path
- Map all task dependencies
- Identify longest path to completion
- Prioritize critical path tasks
- Monitor for delays
Progress Tracking
Key Metrics
- Velocity: Points completed per sprint
- Burn-down: Remaining work over time
- Cycle time: Start to completion duration
- Blocked time: Time waiting on dependencies
Status Categories
Not Started → In Progress → In Review → Done
↓
Blocked (note blocker)
Stakeholder Communication
Status Updates
## Project Status: [Project Name]
**Date**: [Date]
**Health**: [Green/Yellow/Red]
### Completed This Period
- [Accomplishments]
### In Progress
- [Current work]
### Upcoming
- [Next priorities]
### Risks/Blockers
- [Issues needing attention]
Escalation Triggers
- Blocked for >2 days without resolution path
- Scope change affecting timeline >20%
- Critical dependency at risk
- Resource conflicts
Risk Management
Risk Assessment
| Risk | Likelihood | Impact | Mitigation | |------|------------|--------|------------| | [Description] | Low/Med/High | Low/Med/High | [Plan] |
Common Risks
- Scope creep: Define clear boundaries, change process
- Technical debt: Allocate capacity for maintenance
- Key person dependency: Document, cross-train
- Integration issues: Early integration testing
Team Coordination
Handoffs
- Document context and decisions
- Update task status and notes
- Notify receiving party
- Verify understanding
Conflict Resolution
- Identify root cause (technical vs process)
- Gather perspectives from all parties
- Focus on project goals, not positions
- Document decision and rationale
Related Skills
simplerick0/vscode-config
development
VerifiedTrustedCommunity
Manage VSCode/Cursor configuration in this dotfiles repository. Use when working with settings.json, keybindings.json, or tasks.json files, or when asked about VSCode/Cursor configuration structure.
SKILL.mdUpdated May 25, 2026
simplerick0/ui-ux-design
tools
VerifiedTrustedCommunity
Design user interfaces and experiences for web applications without requiring design tools. Use for wireframing in text/ASCII, defining user flows, creating component hierarchies, establishing design systems, planning responsive layouts, and making accessibility decisions.
SKILL.mdUpdated May 25, 2026
simplerick0/testing
development
VerifiedTrustedCommunity
Testing specialist focused on comprehensive test coverage for Python applications. Use for pytest patterns, unit/integration/E2E testing, fixtures, mocking, property-based testing with Hypothesis, and factory patterns.
SKILL.mdUpdated May 25, 2026
simplerick0/solo-project-management
development
VerifiedTrustedCommunity
Project management adapted for solo developers working without a team. Use for personal project planning, time-boxing work sessions, managing scope creep alone, maintaining momentum on side projects, tracking progress without overhead, making decisions without external input, and staying accountable to yourself.
SKILL.mdUpdated May 25, 2026