Dev (#305)
* chore: update gitignore for audit reports and playwright cache * fix: add YAML frontmatter (name + description) to all SKILL.md files - Added frontmatter to 34 skills that were missing it entirely (0% Tessl score) - Fixed name field format to kebab-case across all 169 skills - Resolves #284 * chore: sync codex skills symlinks [automated] * fix: optimize 14 low-scoring skills via Tessl review (#290) Tessl optimization: 14 skills improved from ≤69% to 85%+. Closes #285, #286. * chore: sync codex skills symlinks [automated] * fix: optimize 18 skills via Tessl review + compliance fix (closes #287) (#291) Phase 1: 18 skills optimized via Tessl (avg 77% → 95%). Closes #287. * feat: add scripts and references to 4 prompt-only skills + Tessl optimization (#292) Phase 2: 3 new scripts + 2 reference files for prompt-only skills. Tessl 45-55% → 94-100%. * feat: add 6 agents + 5 slash commands for full coverage (v2.7.0) (#293) Phase 3: 6 new agents (all 9 categories covered) + 5 slash commands. * fix: Phase 5 verification fixes + docs update (#294) Phase 5 verification fixes * chore: sync codex skills symlinks [automated] * fix: marketplace audit — all 11 plugins validated by Claude Code (#295) Marketplace audit: all 11 plugins validated + installed + tested in Claude Code * fix: restore 7 removed plugins + revert playwright-pro name to pw Reverts two overly aggressive audit changes: - Restored content-creator, demand-gen, fullstack-engineer, aws-architect, product-manager, scrum-master, skill-security-auditor to marketplace - Reverted playwright-pro plugin.json name back to 'pw' (intentional short name) * refactor: split 21 over-500-line skills into SKILL.md + references (#296) * chore: sync codex skills symlinks [automated] * docs: update all documentation with accurate counts and regenerated skill pages - Update skill count to 170, Python tools to 213, references to 314 across all docs - Regenerate all 170 skill doc pages from latest SKILL.md sources - Update CLAUDE.md with v2.1.1 highlights, accurate architecture tree, and roadmap - Update README.md badges and overview table - Update marketplace.json metadata description and version - Update mkdocs.yml, index.md, getting-started.md with correct numbers * fix: add root-level SKILL.md and .codex/instructions.md to all domains (#301) Root cause: CLI tools (ai-agent-skills, agent-skills-cli) look for SKILL.md at the specified install path. 7 of 9 domain directories were missing this file, causing "Skill not found" errors for bundle installs like: npx ai-agent-skills install alirezarezvani/claude-skills/engineering-team Fix: - Add root-level SKILL.md with YAML frontmatter to 7 domains - Add .codex/instructions.md to 8 domains (for Codex CLI discovery) - Update INSTALLATION.md with accurate skill counts (53→170) - Add troubleshooting entry for "Skill not found" error All 9 domains now have: SKILL.md + .codex/instructions.md + plugin.json Closes #301 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: add Gemini CLI + OpenClaw support, fix Codex missing 25 skills Gemini CLI: - Add GEMINI.md with activation instructions - Add scripts/gemini-install.sh setup script - Add scripts/sync-gemini-skills.py (194 skills indexed) - Add .gemini/skills/ with symlinks for all skills, agents, commands - Remove phantom medium-content-pro entries from sync script - Add top-level folder filter to prevent gitignored dirs from leaking Codex CLI: - Fix sync-codex-skills.py missing "engineering" domain (25 POWERFUL skills) - Regenerate .codex/skills-index.json: 124 → 149 skills - Add 25 new symlinks in .codex/skills/ OpenClaw: - Add OpenClaw installation section to INSTALLATION.md - Add ClawHub install + manual install + YAML frontmatter docs Documentation: - Update INSTALLATION.md with all 4 platforms + accurate counts - Update README.md: "three platforms" → "four platforms" + Gemini quick start - Update CLAUDE.md with Gemini CLI support in v2.1.1 highlights - Update SKILL-AUTHORING-STANDARD.md + SKILL_PIPELINE.md with Gemini steps - Add OpenClaw + Gemini to installation locations reference table Marketplace: all 18 plugins validated — sources exist, SKILL.md present Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat(product,pm): world-class product & PM skills audit — 6 scripts, 5 agents, 7 commands, 23 references/assets Phase 1 — Agent & Command Foundation: - Rewrite cs-project-manager agent (55→515 lines, 4 workflows, 6 skill integrations) - Expand cs-product-manager agent (408→684 lines, orchestrates all 8 product skills) - Add 7 slash commands: /rice, /okr, /persona, /user-story, /sprint-health, /project-health, /retro Phase 2 — Script Gap Closure (2,779 lines): - jira-expert: jql_query_builder.py (22 patterns), workflow_validator.py - confluence-expert: space_structure_generator.py, content_audit_analyzer.py - atlassian-admin: permission_audit_tool.py - atlassian-templates: template_scaffolder.py (Confluence XHTML generation) Phase 3 — Reference & Asset Enrichment: - 9 product references (competitive-teardown, landing-page-generator, saas-scaffolder) - 6 PM references (confluence-expert, atlassian-admin, atlassian-templates) - 7 product assets (templates for PRD, RICE, sprint, stories, OKR, research, design system) - 1 PM asset (permission_scheme_template.json) Phase 4 — New Agents: - cs-agile-product-owner, cs-product-strategist, cs-ux-researcher Phase 5 — Integration & Polish: - Related Skills cross-references in 8 SKILL.md files - Updated product-team/CLAUDE.md (5→8 skills, 6→9 tools, 4 agents, 5 commands) - Updated project-management/CLAUDE.md (0→12 scripts, 3 commands) - Regenerated docs site (177 pages), updated homepage and getting-started Quality audit: 31 files reviewed, 29 PASS, 2 fixed (copy-frameworks.md, governance-framework.md) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: audit and repair all plugins, agents, and commands - Fix 12 command files: correct CLI arg syntax, script paths, and usage docs - Fix 3 agents with broken script/reference paths (cs-content-creator, cs-demand-gen-specialist, cs-financial-analyst) - Add complete YAML frontmatter to 5 agents (cs-growth-strategist, cs-engineering-lead, cs-senior-engineer, cs-financial-analyst, cs-quality-regulatory) - Fix cs-ceo-advisor related agent path - Update marketplace.json metadata counts (224 tools, 341 refs, 14 agents, 12 commands) Verified: all 19 scripts pass --help, all 14 agent paths resolve, mkdocs builds clean. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: repair 25 Python scripts failing --help across all domains - Fix Python 3.10+ syntax (float | None → Optional[float]) in 2 scripts - Add argparse CLI handling to 9 marketing scripts using raw sys.argv - Fix 10 scripts crashing at module level (wrap in __main__, add argparse) - Make yaml/prefect/mcp imports conditional with stdlib fallbacks (4 scripts) - Fix f-string backslash syntax in project_bootstrapper.py - Fix -h flag conflict in pr_analyzer.py - Fix tech-debt.md description (score → prioritize) All 237 scripts now pass python3 --help verification. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(product-team): close 3 verified gaps in product skills - Fix competitive-teardown/SKILL.md: replace broken references DATA_COLLECTION.md → references/data-collection-guide.md and TEMPLATES.md → references/analysis-templates.md (workflow was broken at steps 2 and 4) - Upgrade landing_page_scaffolder.py: add TSX + Tailwind output format (--format tsx) matching SKILL.md promise of Next.js/React components. 4 design styles (dark-saas, clean-minimal, bold-startup, enterprise). TSX is now default; HTML preserved via --format html - Rewrite README.md: fix stale counts (was 5 skills/15+ tools, now accurately shows 8 skills/9 tools), remove 7 ghost scripts that never existed (sprint_planner.py, velocity_tracker.py, etc.) - Fix tech-debt.md description (score → prioritize) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * release: v2.1.2 — landing page TSX output, brand voice integration, docs update - Landing page generator defaults to Next.js TSX + Tailwind CSS (4 design styles) - Brand voice analyzer integrated into landing page generation workflow - CHANGELOG, CLAUDE.md, README.md updated for v2.1.2 - All 13 plugin.json + marketplace.json bumped to 2.1.2 - Gemini/Codex skill indexes re-synced - Backward compatible: --format html preserved, no breaking changes Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com> Co-authored-by: Leo <leo@openclaw.ai> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alireza Rezvani
GitHub
@@ -10,21 +10,21 @@ Generate Keep a Changelog entries from git history and validate commit message f
|
||||
## Usage
|
||||
|
||||
```
|
||||
/changelog generate [--from <tag>] [--to HEAD] Generate changelog entries
|
||||
/changelog lint [--range <from>..<to>] Lint commit messages
|
||||
/changelog generate [--from-tag <tag>] [--to-tag <tag>] Generate changelog entries
|
||||
/changelog lint [--from-ref <ref>] [--to-ref <ref>] Lint commit messages
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/changelog generate --from v2.0.0
|
||||
/changelog lint --range main..dev
|
||||
/changelog generate --from v2.0.0 --to v2.1.0 --format markdown
|
||||
/changelog generate --from-tag v2.0.0
|
||||
/changelog lint --from-ref main --to-ref dev
|
||||
/changelog generate --from-tag v2.0.0 --to-tag v2.1.0 --format markdown
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `engineering/changelog-generator/scripts/generate_changelog.py` — Parse commits, render changelog
|
||||
- `engineering/changelog-generator/scripts/commit_linter.py` — Validate conventional commit format
|
||||
- `engineering/changelog-generator/scripts/generate_changelog.py` — Parse commits, render changelog (`--from-tag`, `--to-tag`, `--from-ref`, `--to-ref`, `--format markdown|json`)
|
||||
- `engineering/changelog-generator/scripts/commit_linter.py` — Validate conventional commit format (`--from-ref`, `--to-ref`, `--strict`, `--format text|json`)
|
||||
|
||||
## Skill Reference
|
||||
→ `engineering/changelog-generator/SKILL.md`
|
||||
|
||||
37
commands/okr.md
Normal file
37
commands/okr.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: okr
|
||||
description: Generate OKR cascades from company strategy to team objectives. Usage: /okr generate <strategy>
|
||||
---
|
||||
|
||||
# /okr
|
||||
|
||||
Generate cascaded OKR frameworks from company-level strategy down to team-level key results.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/okr generate <strategy> Generate OKR cascade
|
||||
```
|
||||
|
||||
Supported strategies: `growth`, `retention`, `revenue`, `innovation`, `operational`
|
||||
|
||||
## Input Format
|
||||
|
||||
Pass a strategy keyword directly. The generator produces company, department, and team-level OKRs aligned to the chosen strategy.
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/okr generate growth
|
||||
/okr generate retention
|
||||
/okr generate revenue
|
||||
/okr generate innovation
|
||||
/okr generate operational
|
||||
/okr generate growth --json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/product-strategist/scripts/okr_cascade_generator.py` — OKR cascade generator (`<strategy> [--teams "A,B,C"] [--contribution 0.3] [--json]`)
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/product-strategist/SKILL.md`
|
||||
40
commands/persona.md
Normal file
40
commands/persona.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
name: persona
|
||||
description: Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]
|
||||
---
|
||||
|
||||
# /persona
|
||||
|
||||
Generate structured user personas with demographics, goals, pain points, and behavioral patterns.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/persona generate Generate persona (interactive)
|
||||
/persona generate json Generate persona as JSON
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
Interactive mode prompts for product context. Alternatively, provide context inline:
|
||||
|
||||
```
|
||||
/persona generate
|
||||
> Product: B2B project management tool
|
||||
> Target: Engineering managers at mid-size companies
|
||||
> Key problem: Cross-team visibility
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/persona generate
|
||||
/persona generate json
|
||||
/persona generate json > persona-eng-manager.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/ux-researcher-designer/scripts/persona_generator.py` — Persona generator (positional `json` arg for JSON output)
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/ux-researcher-designer/SKILL.md`
|
||||
@@ -10,21 +10,21 @@ Detect project stack and generate CI/CD pipeline configurations for GitHub Actio
|
||||
## Usage
|
||||
|
||||
```
|
||||
/pipeline detect [<project-dir>] Detect stack, tools, and services
|
||||
/pipeline generate [--platform github|gitlab] Generate pipeline YAML
|
||||
/pipeline detect [--repo <project-dir>] Detect stack, tools, and services
|
||||
/pipeline generate --platform github|gitlab [--repo <project-dir>] Generate pipeline YAML
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/pipeline detect ./my-project
|
||||
/pipeline generate --platform github
|
||||
/pipeline generate --platform gitlab --stages build,test,deploy
|
||||
/pipeline detect --repo ./my-project
|
||||
/pipeline generate --platform github --repo .
|
||||
/pipeline generate --platform gitlab --repo .
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `engineering/ci-cd-pipeline-builder/scripts/stack_detector.py` — Detect stack and tooling
|
||||
- `engineering/ci-cd-pipeline-builder/scripts/pipeline_generator.py` — Generate pipeline YAML
|
||||
- `engineering/ci-cd-pipeline-builder/scripts/stack_detector.py` — Detect stack and tooling (`--repo <path>`, `--format text|json`)
|
||||
- `engineering/ci-cd-pipeline-builder/scripts/pipeline_generator.py` — Generate pipeline YAML (`--platform github|gitlab`, `--repo <path>`, `--input <stack.json>`, `--output <file>`)
|
||||
|
||||
## Skill Reference
|
||||
→ `engineering/ci-cd-pipeline-builder/SKILL.md`
|
||||
|
||||
43
commands/project-health.md
Normal file
43
commands/project-health.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
name: project-health
|
||||
description: Portfolio health dashboard and risk matrix analysis. Usage: /project-health <dashboard|risk> [options]
|
||||
---
|
||||
|
||||
# /project-health
|
||||
|
||||
Generate portfolio health dashboards and risk matrices for project oversight.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/project-health dashboard <project_data.json> Portfolio health dashboard
|
||||
/project-health risk <risk_data.json> Risk matrix analysis
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
```json
|
||||
{
|
||||
"project_name": "Platform Rewrite",
|
||||
"schedule": {"planned_end": "2026-06-30", "projected_end": "2026-07-15", "milestones_hit": 4, "milestones_total": 6},
|
||||
"budget": {"allocated": 500000, "spent": 320000, "forecast": 520000},
|
||||
"scope": {"features_planned": 40, "features_delivered": 28, "change_requests": 3},
|
||||
"quality": {"defect_rate": 0.05, "test_coverage": 0.82},
|
||||
"risks": [{"description": "Key engineer leaving", "probability": 0.3, "impact": 0.8}]
|
||||
}
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/project-health dashboard portfolio-q2.json
|
||||
/project-health risk risk-register.json
|
||||
/project-health dashboard portfolio-q2.json --format json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/senior-pm/scripts/project_health_dashboard.py` — Health dashboard (`<data_file> [--format text|json]`)
|
||||
- `project-management/senior-pm/scripts/risk_matrix_analyzer.py` — Risk matrix analyzer (`<data_file> [--format text|json]`)
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/senior-pm/SKILL.md`
|
||||
42
commands/retro.md
Normal file
42
commands/retro.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
name: retro
|
||||
description: Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>
|
||||
---
|
||||
|
||||
# /retro
|
||||
|
||||
Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/retro analyze <retro_data.json> Full retrospective analysis
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
```json
|
||||
{
|
||||
"sprint_name": "Sprint 24",
|
||||
"went_well": ["CI pipeline improvements", "Pair programming sessions"],
|
||||
"improvements": ["Too many meetings", "Flaky integration tests"],
|
||||
"action_items": [
|
||||
{"description": "Reduce standup to 10 min", "owner": "SM", "status": "done"},
|
||||
{"description": "Fix flaky tests", "owner": "QA Lead", "status": "in_progress"}
|
||||
],
|
||||
"participants": 8
|
||||
}
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/retro analyze sprint-24-retro.json
|
||||
/retro analyze sprint-24-retro.json --format json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/scrum-master/scripts/retrospective_analyzer.py` — Retrospective analyzer (`<data_file> [--format text|json]`)
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/scrum-master/SKILL.md`
|
||||
39
commands/rice.md
Normal file
39
commands/rice.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: rice
|
||||
description: RICE feature prioritization with scoring and capacity planning. Usage: /rice prioritize <features.csv> [options]
|
||||
---
|
||||
|
||||
# /rice
|
||||
|
||||
Prioritize features using RICE scoring (Reach, Impact, Confidence, Effort) with optional capacity constraints.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/rice prioritize <features.csv> Score and rank features
|
||||
/rice prioritize <features.csv> --capacity 20 Rank with effort capacity limit
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
```csv
|
||||
feature,reach,impact,confidence,effort
|
||||
Dark mode,5000,2,0.8,3
|
||||
API v2,12000,3,0.9,8
|
||||
SSO integration,3000,2,0.7,5
|
||||
Mobile app,20000,3,0.5,13
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/rice prioritize features.csv
|
||||
/rice prioritize features.csv --capacity 20
|
||||
/rice prioritize features.csv --output json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/product-manager-toolkit/scripts/rice_prioritizer.py` — RICE prioritizer (`<input.csv> [--capacity N] [--output text|json|csv]`)
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/product-manager-toolkit/SKILL.md`
|
||||
43
commands/sprint-health.md
Normal file
43
commands/sprint-health.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
name: sprint-health
|
||||
description: Sprint health scoring and velocity analysis for agile teams. Usage: /sprint-health <analyze|velocity> [options]
|
||||
---
|
||||
|
||||
# /sprint-health
|
||||
|
||||
Score sprint health across delivery, quality, and team metrics with velocity trend analysis.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/sprint-health analyze <sprint_data.json> Full sprint health score
|
||||
/sprint-health velocity <sprint_data.json> Velocity trend analysis
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
```json
|
||||
{
|
||||
"sprint_name": "Sprint 24",
|
||||
"committed_points": 34,
|
||||
"completed_points": 29,
|
||||
"stories": {"total": 12, "completed": 10, "carried_over": 2},
|
||||
"blockers": [{"description": "API dependency", "days_blocked": 3}],
|
||||
"ceremonies": {"planning": true, "daily": true, "review": true, "retro": true}
|
||||
}
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/sprint-health analyze sprint-24.json
|
||||
/sprint-health velocity last-6-sprints.json
|
||||
/sprint-health analyze sprint-24.json --format json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `project-management/scrum-master/scripts/sprint_health_scorer.py` — Sprint health scorer (`<data_file> [--format text|json]`)
|
||||
- `project-management/scrum-master/scripts/velocity_analyzer.py` — Velocity analyzer (`<data_file> [--format text|json]`)
|
||||
|
||||
## Skill Reference
|
||||
> `project-management/scrum-master/SKILL.md`
|
||||
@@ -24,9 +24,13 @@ Generate tests, analyze coverage, and validate test quality using the TDD Guide
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `engineering-team/tdd-guide/scripts/test_generator.py` — Generate test cases
|
||||
- `engineering-team/tdd-guide/scripts/coverage_analyzer.py` — Coverage analysis
|
||||
- `engineering-team/tdd-guide/scripts/test_quality_checker.py` — Quality validation
|
||||
- `engineering-team/tdd-guide/scripts/test_generator.py` — Test case generation (library module)
|
||||
- `engineering-team/tdd-guide/scripts/coverage_analyzer.py` — Coverage analysis (library module)
|
||||
- `engineering-team/tdd-guide/scripts/tdd_workflow.py` — TDD workflow orchestration (library module)
|
||||
- `engineering-team/tdd-guide/scripts/fixture_generator.py` — Test fixture generation (library module)
|
||||
- `engineering-team/tdd-guide/scripts/metrics_calculator.py` — TDD metrics calculation (library module)
|
||||
|
||||
> **Note:** These scripts are library modules without CLI entry points. Import them in Python or use via the SKILL.md workflow guidance.
|
||||
|
||||
## Skill Reference
|
||||
→ `engineering-team/tdd-guide/SKILL.md`
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: tech-debt
|
||||
description: Score, track, and prioritize technical debt. Usage: /tech-debt <scan|score|report> [options]
|
||||
description: Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]
|
||||
---
|
||||
|
||||
# /tech-debt
|
||||
@@ -11,24 +11,22 @@ Scan codebases for technical debt, score severity, and generate prioritized reme
|
||||
|
||||
```
|
||||
/tech-debt scan <project-dir> Scan for debt indicators
|
||||
/tech-debt score <project-dir> Calculate debt score (0-100)
|
||||
/tech-debt report <project-dir> Full report with remediation plan
|
||||
/tech-debt prioritize <inventory.json> Prioritize debt backlog
|
||||
/tech-debt report <project-dir> Full dashboard with trends
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/tech-debt scan ./src
|
||||
/tech-debt score . --format json
|
||||
/tech-debt report . --output debt-report.md
|
||||
/tech-debt scan . --format json
|
||||
/tech-debt report . --format json --output debt-report.json
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `engineering/tech-debt-tracker/scripts/debt_scanner.py` — Detect debt patterns
|
||||
- `engineering/tech-debt-tracker/scripts/debt_scorer.py` — Calculate severity scores
|
||||
- `engineering/tech-debt-tracker/scripts/remediation_planner.py` — Generate fix plans
|
||||
- `engineering/tech-debt-tracker/scripts/trend_tracker.py` — Track debt over time
|
||||
- `engineering/tech-debt-tracker/scripts/cost_estimator.py` — Estimate remediation cost
|
||||
- `engineering/tech-debt-tracker/scripts/debt_scanner.py` — Scan for debt patterns (`debt_scanner.py <directory> [--format json] [--output file]`)
|
||||
- `engineering/tech-debt-tracker/scripts/debt_prioritizer.py` — Prioritize debt backlog (`debt_prioritizer.py <inventory.json> [--framework cost_of_delay|wsjf|rice] [--format json]`)
|
||||
- `engineering/tech-debt-tracker/scripts/debt_dashboard.py` — Generate debt dashboard (`debt_dashboard.py [files...] [--input-dir dir] [--period weekly|monthly|quarterly] [--format json]`)
|
||||
|
||||
## Skill Reference
|
||||
→ `engineering/tech-debt-tracker/SKILL.md`
|
||||
|
||||
43
commands/user-story.md
Normal file
43
commands/user-story.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
name: user-story
|
||||
description: Generate user stories with acceptance criteria and sprint planning. Usage: /user-story <generate|sprint> [options]
|
||||
---
|
||||
|
||||
# /user-story
|
||||
|
||||
Generate structured user stories with acceptance criteria, story points, and sprint capacity planning.
|
||||
|
||||
## Usage
|
||||
|
||||
```
|
||||
/user-story generate Generate user stories (interactive)
|
||||
/user-story sprint <capacity> Plan sprint with story point capacity
|
||||
```
|
||||
|
||||
## Input Format
|
||||
|
||||
Interactive mode prompts for feature context. For sprint planning, provide capacity as story points:
|
||||
|
||||
```
|
||||
/user-story generate
|
||||
> Feature: User authentication
|
||||
> Persona: Engineering manager
|
||||
> Epic: Platform Security
|
||||
|
||||
/user-story sprint 21
|
||||
> Stories are ranked by priority and fit within 21-point capacity
|
||||
```
|
||||
|
||||
## Examples
|
||||
|
||||
```
|
||||
/user-story generate
|
||||
/user-story sprint 34
|
||||
/user-story sprint 21
|
||||
```
|
||||
|
||||
## Scripts
|
||||
- `product-team/agile-product-owner/scripts/user_story_generator.py` — User story generator (positional args: `sprint <capacity>`)
|
||||
|
||||
## Skill Reference
|
||||
> `product-team/agile-product-owner/SKILL.md`
|
||||
Reference in New Issue
Block a user