From the author
Use when implementing from a plan, spec, clear build request, or settled ticket, orchestrated or standalone. Don't use for open-ended debugging (figure-it-out), exploration, or read-only research.
Install
npx skills add OutlineDriven/outline-driven-development --skill work -a claude-code
Installs to .claude/skills/work/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- researchOyadotAI/oya-browserThis skill should be used when researching a technical question, checking current API facts, comparing documented capabilities, or gathering primary-source evidence for a decision.Science★ 351
- research-craftnik1t7n/research-craft-skillUse when planning, reviewing, or improving research work: choosing research problems, designing ML/AI experiments, reading papers, building experiment loops, analyzing outputs, writing research notes, or turning vague curiosity into a disciplined research plan. Emphasizes avoiding absorbed problems, upgrading information inputs beyond shared reading lists, and reasoning backward from outcomes the researcher genuinely wants to exist.Science★ 50
- reviewhashgraph-online/awesome-codex-pluginsGive advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.Engineering★ 1.4K
- implement-specOutlineDriven/outline-driven-developmentUse when a ticket DAG from a complete specification needs parallel execution into a green draft PR. Not for a settled ticket with no spec: use work. Not for ticket decomposition: use to-tickets.Planning★ 54
- write-planbrycewang-stanford/Auto-Empirical-Research-SkillsUse when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria. Produces a research execution plan organized in canonical research phases — collection, preparation, analysis, robustness, writing, submission.Writing★ 4.8K
- devheliohq/shipImplement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first.Testing★ 93
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in