skills/okr/SKILL.md
Create quarterly OKRs based on team goals and role. Generates 3 Objectives with 3 Key Results each (9 total), with 70%/100% achievement criteria.
npx skillsauth add sc30gsw/claude-code-customes okrInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Advanced interactive command that helps create individual quarterly OKRs based on team-level goals.
/okr --role <role> "<team-goals>" [options]
| Argument | Description |
|----------|-------------|
| --role <role> | Role (engineer, pm, designer, qa, data-analyst, etc.) |
| <team-goals> | Team-level goals (natural language text) |
| Option | Description |
|--------|-------------|
| --sample <path> | Reference OKR sample file |
| --team-okr <path> | Reference team OKR file |
| --previous <path> | Reference previous quarter OKR |
| Option | Description |
|--------|-------------|
| --output <path> | Output file path |
| --format <type> | Output format: markdown/json/yaml |
| Option | Description |
|--------|-------------|
| --interactive | Interactive OKR creation mode |
| --refine | Refine vague goals through questions |
# Basic usage
/okr --role engineer "20% revenue increase, NPS +10, 2 new product launches"
# With sample reference
/okr --role engineer "売上20%増加" --sample ./okrs/samples/engineer.md
# Interactive mode with persistence
/okr --role engineer --interactive --persist
Each KR includes:
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
testing
# sdd-workflow — Workflow Status Dashboard ## Slash Command ``` /sdd-workflow [slug] ``` ## Purpose Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files. --- ## This Skill is Read-Only `sdd-workflow` never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill. --- ## Usage: Specific Feature ``` /sdd-workflo
content-media
# sdd-tasks **Slash command**: `/sdd-tasks <slug>` **Purpose**: Generate `tasks.md` (TASK-001..N) and `progress.md` from `requirements.md` and `design.md`. --- ## Prerequisites - `.claude/specs/<slug>/requirements.md` must exist - `.claude/specs/<slug>/design.md` must exist (run `/sdd-design` first) --- ## Steps ### 1. Read spec inputs ``` .claude/specs/<slug>/requirements.md .claude/specs/<slug>/design.md ``` Extract: - Every REQ-XXX ID with its acceptance criteria - Every design sect
development
# sdd-review — Post-Implementation Code Review ## Slash Command ``` /sdd-review <slug> ``` ## Purpose Run code review and security review on all changes introduced by the feature branch. Append structured findings to `review.md`. Does NOT auto-apply fixes — only proposes them. --- ## Prerequisites - `sdd-impl` has completed: all tasks in `progress.md` are `done` (or at least one is `done`; partial reviews are allowed). - The feature branch must have at least one commit ahead of `main`. -