skillstore-cli 1.0.0

package/data/free-skills/devflow-agile/plugin/skills/developer/references/debugging-methodology.md

@@ -0,0 +1,191 @@
+# Debugging Methodology
+
+## Systematic Debugging Process
+
+Follow this 6-step process for every bug. Skipping steps leads to "fix one bug, create two more."
+
+### Step 1: Reproduce Reliably
+- **Get the exact reproduction steps** from the reporter (browser, OS, user role, data state)
+- Reproduce in your local environment BEFORE reading the code
+- If you cannot reproduce, gather more data (logs, screenshots, network traces) — do not guess
+- Write down the reproduction steps — you will need them for the regression test
+
+### Step 2: Isolate the Scope
+- **Narrow down**: which service? which module? which function?
+- Use binary search: disable half the system, check if bug persists, narrow further
+- Check: Is this a frontend issue, backend issue, or data issue?
+- Check recent changes: `git log --since="3 days ago" -- path/to/module`
+
+### Step 3: Form a Hypothesis
+- Based on the symptoms, propose ONE possible cause
+- State it explicitly: "I think the bug is caused by X because Y"
+- Design a test for this hypothesis (add a log, change a value, add a breakpoint)
+
+### Step 4: Test the Hypothesis
+- Make ONE change at a time — changing multiple things makes it impossible to know what fixed it
+- If your hypothesis is wrong, gather the new evidence and form another one
+- Track what you have tried: keep a scratch note of hypotheses tested and results
+
+### Step 5: Fix the Root Cause
+- Fix the actual cause, not the symptom
+- Ask: "Why did this happen?" If the answer reveals a deeper issue, fix that too
+- Check for the same pattern elsewhere: if this bug exists in `createUser`, does it exist in `updateUser` too?
+
+### Step 6: Verify and Prevent
+- Write a **regression test** that fails without the fix and passes with it
+- Verify the fix does not break adjacent functionality (run full test suite)
+- Update documentation if the bug revealed a non-obvious behavior
+- Consider: should we add monitoring/alerting for this class of issue?
+
+## Root Cause Analysis Techniques
+
+### The 5 Whys
+Start with the symptom and ask "Why?" repeatedly until you reach the root cause.
+
+**Example:**
+1. Why did the checkout fail? → The payment API returned a 500 error
+2. Why did the payment API return 500? → The request body had a null `currency` field
+3. Why was `currency` null? → The frontend sent the order without the currency when the user used a saved card
+4. Why was currency missing for saved cards? → The saved card flow skips the currency selection step
+5. Why does saved card flow skip currency selection? → The flow was copied from single-currency version and never updated for multi-currency
+
+**Root cause**: Missing multi-currency support in the saved card checkout flow.
+**Fix**: Add currency to saved card payload, with a fallback to user's default currency.
+
+### Fault Tree Analysis
+For complex bugs with multiple contributing factors, draw a tree:
+```
+[Checkout Failure]
+├── [Payment API 500]
+│   ├── [Null currency in request]
+│   │   └── [Saved card flow missing currency]
+│   └── [No input validation on API]
+│       └── [Validation was skipped for "trusted" internal calls]
+└── [No retry mechanism]
+    └── [Transient failures also cause checkout failure]
+```
+This reveals multiple fixes: add currency, add validation, add retry.
+
+## Debugging Tools and Strategies by Language
+
+### JavaScript / TypeScript (Node.js)
+| Tool | Usage |
+|------|-------|
+| `console.log` with JSON.stringify | Quick inspection (remove before committing) |
+| Node.js `--inspect` + Chrome DevTools | Breakpoints, step-through, variable inspection |
+| VS Code debugger | Attach to running process, conditional breakpoints |
+| `DEBUG=*` environment variable | Enable debug logging in Express/Koa and libraries |
+| Network tab (browser) | Inspect request/response payloads, timing, headers |
+
+### JavaScript / TypeScript (Frontend)
+| Tool | Usage |
+|------|-------|
+| React DevTools | Component tree, props/state inspection, re-render highlighting |
+| Redux DevTools | Action history, state diff, time-travel debugging |
+| `Performance` tab | Identify slow renders, layout thrashing, long tasks |
+| `console.table()` | Visualize arrays/objects in console |
+| Source maps | Debug original TypeScript in browser even with bundled output |
+
+### Python
+| Tool | Usage |
+|------|-------|
+| `pdb` / `breakpoint()` | Built-in debugger, step through code |
+| `ipdb` | Enhanced pdb with autocomplete and syntax highlighting |
+| VS Code Python debugger | GUI debugging with variable watches |
+| `logging` module | Structured logging with levels (avoid bare `print()`) |
+| `traceback.print_exc()` | Full stack trace in exception handlers |
+
+### Java / Kotlin
+| Tool | Usage |
+|------|-------|
+| IntelliJ IDEA debugger | Breakpoints, evaluate expression, hot-swap code |
+| Remote debugging (JDWP) | Attach debugger to running JVM in staging |
+| `jstack` | Thread dump for deadlock/hang analysis |
+| `jmap` + `jhat` | Heap dump for memory analysis |
+| Logging (SLF4J + Logback) | Structured logging with MDC for request context |
+
+## Common Bug Patterns in Web Applications
+
+| Pattern | Symptoms | Typical Cause | Fix |
+|---------|----------|---------------|-----|
+| N+1 Query | Page loads slowly, DB CPU high | ORM lazy-loading in a loop | Use eager loading, batch queries, or joins |
+| Race condition | Intermittent failures, data corruption | Concurrent access to shared state | Add locks, use transactions, or idempotency keys |
+| Stale cache | User sees old data after update | Cache not invalidated on write | Invalidate/update cache on write, add TTL |
+| Off-by-one | Missing first/last item in lists, wrong counts | Array index or pagination math error | Review loop boundaries, test edge cases (0, 1, max) |
+| Null reference | Random crashes on certain data | Missing null check on optional field | Add null checks, use Optional/Maybe types, fix data |
+| Timezone mismatch | Events appear on wrong date | Mixing UTC and local time | Store UTC in DB, convert to local only in presentation |
+| CORS error | API calls blocked in browser | Missing CORS headers on backend | Configure CORS middleware for allowed origins |
+| Memory leak | Server/app slows over time, OOM crash | Unclosed connections, growing arrays, event listener accumulation | Profile heap, find retained references, add cleanup |
+
+## Performance Profiling Basics
+
+### When to Profile
+- Response time exceeds SLA (e.g., API > 500ms)
+- Memory usage grows continuously (potential leak)
+- CPU usage stays high even at low traffic
+- Users report "slowness" — quantify before optimizing
+
+### Profiling Strategy
+1. **Measure first** — do not optimize based on intuition
+2. **Profile in realistic conditions** — use production-like data volumes
+3. **Focus on the bottleneck** — Amdahl's Law: optimizing a 5% piece of the process yields negligible improvement
+4. **Benchmark before and after** — prove the optimization worked
+
+### Common Performance Wins
+| Area | Quick Check | Optimization |
+|------|------------|-------------|
+| Database | Enable slow query log, check EXPLAIN plans | Add indexes, reduce query count, optimize joins |
+| API | Measure response times per endpoint | Add caching (Redis), paginate results, compress responses |
+| Frontend | Lighthouse score, bundle size analysis | Code splitting, lazy loading, image optimization |
+| Memory | Heap snapshot over time | Fix leaks (unclosed connections, growing caches, event listeners) |
+
+## Memory Leak Detection
+
+### Symptoms
+- Application memory grows steadily over hours/days
+- Garbage collection pauses become longer and more frequent
+- Eventually: OOM (Out of Memory) crash or extreme slowness
+
+### Common Causes
+| Cause | Example | Detection |
+|-------|---------|-----------|
+| Event listener accumulation | Adding listeners in a loop without removing | Heap snapshot: growing EventEmitter or listener count |
+| Unclosed connections | DB connections, HTTP clients not released | Monitor connection pool stats, check for pool exhaustion |
+| Growing global collections | Pushing to a module-level array/map indefinitely | Heap snapshot: large Array or Map growing between snapshots |
+| Closure leaks | Closures referencing large objects that should be GC'd | Heap snapshot: retaining paths to unexpected objects |
+| Circular references (older engines) | Object A references B, B references A | Use WeakMap/WeakRef for caches, break cycles on cleanup |
+
+### Detection Process
+1. Take heap snapshot at startup
+2. Run realistic load for 10 minutes
+3. Take second heap snapshot
+4. Compare: look for objects that grew significantly in count or retained size
+5. Trace the retaining path to find why objects are not being garbage collected
+
+## Race Condition Identification
+
+### Symptoms
+- Bug appears intermittently, not every time
+- Bug appears under load but not in local testing
+- Data corruption: two operations conflict (double-charge, double-booking)
+
+### Common Locations
+| Location | Example | Prevention |
+|----------|---------|-----------|
+| Database reads then writes | Read balance, check, write → two requests read same balance | Use DB transactions with appropriate isolation level |
+| File system operations | Two processes write the same file | Use file locks or atomic rename |
+| Shared in-memory state | Two requests modify the same cache entry | Use atomic operations, lock, or queue |
+| UI state | User double-clicks submit button | Disable button on first click, use idempotency key |
+| Distributed systems | Two services process the same event | Idempotency keys, distributed locks (Redis SETNX) |
+
+## Production Debugging Best Practices
+
+| Rule | Guideline |
+|------|-----------|
+| **Never debug with code changes in production** | Use logging, feature flags, or diagnostic endpoints |
+| **Structured logs are your best friend** | Request ID in every log line lets you trace a request end-to-end |
+| **Reproduce in staging first** | If you can reproduce in staging, debug there — not in production |
+| **Time-box production investigation** | Set a timer: 30 min to find root cause, then escalate if stuck |
+| **Communicate status updates** | Every 30 min during an incident: what we know, what we are doing, ETA |
+| **Post-incident review** | Within 48 hours: timeline, root cause, fix, preventive measures |
+| **Avoid blame** | Focus on "how do we prevent this" not "who caused this" |

package/data/free-skills/devflow-agile/template/agents/agile-coach.md

@@ -0,0 +1,76 @@
+---
+name: agile-coach
+description: Use this agent to oversee the entire Agile development process — coordinates all 10 role-based skills, ensures ceremonies happen, tracks team health, and drives continuous improvement across sprints.
+tools: Glob, Grep, LS, Read, Edit, Write, WebFetch
+---
+
+You are a Senior Agile Coach with 12+ years of experience leading Agile transformations in IT outsourcing companies. You oversee the entire development lifecycle and coordinate all team roles.
+
+## Core Responsibilities
+
+### 1. Sprint Management
+- Activate `scrum-master` skill for ceremony facilitation
+- Activate `project-manager` skill for planning and tracking
+- Ensure sprint goals are clear and achievable
+- Track velocity and burndown across sprints
+
+### 2. Requirements & Design
+- Activate `business-analyst` skill for story writing
+- Activate `solution-architect` skill for technical decisions
+- Ensure stories meet INVEST criteria before sprint commitment
+- Validate architecture decisions align with project goals
+
+### 3. Development Oversight
+- Activate `tech-lead` skill for code quality
+- Activate `developer` skill for implementation guidance
+- Activate `team-lead` skill for team coordination
+- Ensure Definition of Done is met
+
+### 4. Quality Assurance
+- Activate `qa-tester` skill for test strategy
+- Activate `ui-ux-designer` skill for design review
+- Ensure testing is thorough and not bypassed
+- Validate accessibility compliance
+
+### 5. Infrastructure & Delivery
+- Activate `devops-engineer` skill for CI/CD and deployment
+- Ensure environments are stable
+- Monitor deployment success and rollback readiness
+
+## Operational Guidelines
+
+- Use role skills as needed — not all roles apply to every task
+- Focus on removing impediments and enabling the team
+- Track metrics without micromanaging
+- Promote self-organization while ensuring accountability
+
+## Error Recovery
+
+Reference: `rules/development-rules.md` and `protocols/error-recovery.md`
+
+### Retry Policy
+- Max retries: from config.thresholds.maxRetries (default: 3)
+- Between retries: analyze what went wrong, adjust approach
+- After max retries: STOP, report with diagnostic context
+
+### Escalation
+| Failure | Action |
+|---------|--------|
+| Sprint goal unclear | Ask user/PO for clarification |
+| Story too large to estimate | Recommend splitting, activate business-analyst skill |
+| Blocker not resolvable by team | Escalate to user with context and suggested resolution |
+| Test failures blocking sprint | Activate qa-tester skill for analysis, then developer skill for fix |
+| Deployment failure | Activate devops-engineer skill, follow error-recovery protocol |
+
+## Checkpoint Protocol
+
+After completing each ceremony/milestone:
+1. Update sprint status
+2. Log: ceremony outcome, decisions made, action items
+3. If interrupted: next session can resume from last completed ceremony
+
+## Model Usage
+- Ceremony facilitation: primary model
+- Metrics calculation: lightweight model
+- Research/background tasks: lightweight model
+- Fall back per config if primary unavailable

package/data/free-skills/devflow-agile/template/workflows/agile-sprint-workflow.md

@@ -0,0 +1,81 @@
+# Agile Sprint Workflow
+
+Complete sprint lifecycle from planning through retrospective.
+
+## Phase 1: Sprint Planning
+
+1. **Backlog Refinement**
+   - `agile-coach` activates `business-analyst` skill
+   - Review and refine backlog items
+   - Ensure stories have acceptance criteria
+   - Estimate using planning poker / t-shirt sizing
+
+2. **Sprint Planning Meeting**
+   - `agile-coach` activates `scrum-master` skill
+   - Set sprint goal
+   - Team commits to stories based on capacity
+   - `agile-coach` activates `project-manager` for capacity check
+   - Break stories into tasks
+
+3. **Technical Planning**
+   - `agile-coach` activates `solution-architect` skill for design decisions
+   - `agile-coach` activates `tech-lead` skill for standards review
+   - Identify technical spikes needed
+
+## Phase 2: Sprint Execution
+
+4. **Daily Development**
+   - `agile-coach` activates `developer` skill for implementation
+   - `agile-coach` activates `team-lead` for task coordination
+   - Daily standups via `scrum-master` skill
+   - Track progress on sprint board
+
+5. **Continuous Quality**
+   - `agile-coach` activates `qa-tester` for test execution
+   - `agile-coach` activates `tech-lead` for code review
+   - `agile-coach` activates `ui-ux-designer` for design review
+   - Fix bugs within sprint when possible
+
+6. **Infrastructure Support**
+   - `agile-coach` activates `devops-engineer` for deployment
+   - Maintain CI/CD pipeline
+   - Environment issue resolution
+
+## Phase 3: Sprint Closure
+
+7. **Sprint Review**
+   - `agile-coach` activates `scrum-master` for ceremony
+   - Demo completed work to stakeholders
+   - Collect feedback
+   - `agile-coach` activates `project-manager` for metrics
+
+8. **Sprint Retrospective**
+   - `agile-coach` activates `scrum-master` for facilitation
+   - Identify improvements
+   - Create action items with owners
+   - Review previous retro actions
+
+## Quality Gates
+
+- **Before Sprint Start**: All committed stories refined and estimated
+- **During Sprint**: Daily standup, blocker resolution < 24h
+- **Before Review**: All committed stories meet DoD
+- **After Retro**: At least 2 actionable improvement items
+
+## Error Recovery
+
+Reference: `protocols/error-recovery.md`
+
+### Common Sprint Failures
+| Failure | Recovery |
+|---------|----------|
+| Stories not refined before planning | Pause planning, run refinement first |
+| Velocity drop > 20% | Analyze root cause (team changes? scope creep? technical debt?) |
+| Sprint goal missed | Carry over incomplete stories, identify WHY at retro |
+| Build/deploy failure mid-sprint | devops-engineer skill → diagnose → fix → resume |
+| Critical bug in production | Stop sprint work, triage bug, hotfix, then resume |
+
+### Retry Limits
+- Ceremony facilitation: no retry needed (just adjust format)
+- Technical tasks: max 3 retries per task
+- After 3 failed retries: escalate to user, do not continue silently

package/data/free-skills/devflow-bootstrap/manifest.json

@@ -0,0 +1,8 @@
+{
+  "name": "@skillstore/devflow-bootstrap",
+  "version": "1.0.0",
+  "skills": ["project-scaffold", "cicd-setup", "env-configurator", "code-standards-init"],
+  "freeSkills": ["project-scaffold"],
+  "commands": ["bootstrap", "bootstrap/auto"],
+  "modes": ["plugin", "template"]
+}

package/data/free-skills/devflow-bootstrap/plugin/commands/bootstrap/auto.md

@@ -0,0 +1,31 @@
+---
+description: Full automated Sprint 0 — scaffold + standards + environments + CI/CD in one run
+argument-hint: [tech stack description]
+---
+
+## Your Mission
+
+<task>
+$ARGUMENTS
+</task>
+
+## Automated Workflow
+
+Execute the full bootstrap workflow sequentially:
+
+1. **Tech Stack Confirmation** — Parse description, confirm with user
+2. **Scaffold** — Activate `project-scaffold` skill → generate structure
+3. **Standards + Environment** (parallel):
+   - Activate `code-standards-init` skill → linter, formatter, hooks
+   - Activate `env-configurator` skill → .env templates, Docker setup
+4. **CI/CD** — Activate `cicd-setup` skill → pipeline files
+5. **Verify** — Run lint, format check, validate YAML configs
+6. **Report** — Present file tree, required secrets, getting-started steps
+
+## Quality Gate
+
+Before reporting success, verify:
+- [ ] Linter runs with zero errors
+- [ ] Formatter reports no changes needed
+- [ ] CI workflow YAML is syntactically valid
+- [ ] All environment templates have matching documentation

package/data/free-skills/devflow-bootstrap/plugin/commands/bootstrap.md

@@ -0,0 +1,38 @@
+---
+description: Sprint 0 project setup — scaffold project, configure CI/CD, set up environments and code standards
+argument-hint: [tech stack or task description]
+---
+
+## Your Mission
+
+<task>
+$ARGUMENTS
+</task>
+
+## Workflow
+
+Analyze the task and route to the appropriate bootstrap skill:
+
+1. **Understand the request** — What setup activity is needed?
+2. **Route to skill** — Based on the task:
+   - Project creation → Activate `project-scaffold` skill
+   - CI/CD pipeline → Activate `cicd-setup` skill
+   - Environment setup → Activate `env-configurator` skill
+   - Linting/formatting → Activate `code-standards-init` skill
+3. **Orchestrate if needed** — For full Sprint 0 setup:
+   - Start with project-scaffold (foundation)
+   - Run code-standards-init + env-configurator (parallel)
+   - Finalize with cicd-setup (needs project structure)
+
+## Sub-commands
+
+- `/bootstrap:auto [tech-stack]` — Full automated Sprint 0 setup
+- `/bootstrap:scaffold [tech-stack]` — Create project structure only
+- `/bootstrap:cicd [platform]` — Generate CI/CD pipeline only
+- `/bootstrap:standards` — Configure code quality tooling only
+
+## Important
+
+- Confirm tech stack before scaffolding
+- Verify generated configs have valid syntax
+- List all required secrets and env vars at the end

package/data/free-skills/devflow-bootstrap/plugin/commands/devflow.md

@@ -0,0 +1,20 @@
+---
+description: DevFlow smart router — automatically routes to the right DevFlow package
+argument-hint: [task description]
+---
+
+## Smart Routing
+
+<task>
+$ARGUMENTS
+</task>
+
+Analyze the task and route to the appropriate DevFlow command:
+
+| Keywords/Context | Route To |
+|------------------|----------|
+| scaffold, setup, init, Sprint 0, new project, CI/CD, environment | `/bootstrap` |
+| presale, RFP, proposal, estimate, pricing | `/presale` |
+| sprint, standup, agile, backlog, scrum | `/agile` |
+| handover, maintenance, retrospective, post-project | `/postproject` |
+| PDF, Excel, document, parse, generate report | `/docs` |

package/data/free-skills/devflow-bootstrap/plugin/skills/project-scaffold/SKILL.md

@@ -0,0 +1,56 @@
+# Project Scaffold
+
+Generate project structure for any tech stack: directories, config files, boilerplate code.
+
+## Triggers
+
+- New project setup
+- Sprint 0 / project kickoff
+- Tech stack decision made
+- Need to create project from scratch
+- Migrating to new framework
+
+## Process
+
+### 1. Tech Stack Identification
+- Parse user description for framework, language, database
+- If ambiguous, ask user to confirm
+- Check for monorepo vs single-project
+
+### 2. Template Selection
+- Match tech stack to reference templates in `references/stack-templates.md`
+- Combine multiple templates if needed (e.g., Next.js frontend + NestJS backend)
+- Apply project-specific customizations
+
+### 3. Structure Generation
+- Create directory tree following template
+- Generate boilerplate files (entry points, configs, types)
+- Add placeholder README, .gitignore, .env.example
+
+### 4. Config Setup
+- Generate tsconfig.json / pyproject.toml / build.gradle as needed
+- Setup package manager config (package.json, requirements.txt, go.mod)
+- Configure path aliases, module resolution
+
+### 5. Verification
+- Verify all directories created
+- Verify config files have valid syntax
+- List generated files for user review
+
+## Output Format
+
+```
+Created project structure:
+├── src/
+│   ├── ...
+├── config files...
+├── .gitignore
+├── .env.example
+└── README.md
+
+Total: X directories, Y files
+```
+
+## References
+- `references/stack-templates.md` — Project templates by tech stack
+- `assets/sample-output.md` — Sample scaffold output