ownyourcode: Command for Claude Code

.claude/commands/own/feature.md

feature is a command for Claude Code from DanielPodolsky/ownyourcode. It costs 10 tokens per session (5,611 once invoked), scanned A, original, MIT.

A command for creating a feature specification through Spec-Driven Development, a process where requirements and design are written before implementation begins. It produces a plan that the developer reviews and fills in with missing details.

In plain words
What is it for?
Use it to advance a planned roadmap item into a reviewed specification, design, and task list in the project's dashboard.
Why use it?
It turns a broad feature idea into agreed requirements, design decisions, and implementation tasks before code is written.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is DanielPodolsky/ownyourcode's own configuration. It tells Claude Code how to work on ownyourcode itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ownyourcode configures →

Reuse

Borrowing it

Nothing to install: this file belongs to DanielPodolsky/ownyourcode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/.claude/commands/own/feature.md
Clone the repo
git clone --depth 1 https://github.com/DanielPodolsky/ownyourcode

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for feature

README.md
[![agentmods](https://agentmods.dev/badge/commands/danielpodolsky/ownyourcode/feature/github.svg)](https://agentmods.dev/commands/danielpodolsky/ownyourcode/feature)
Your own site
<a href="https://agentmods.dev/commands/danielpodolsky/ownyourcode/feature"><img src="https://agentmods.dev/badge/commands/danielpodolsky/ownyourcode/feature/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for feature

Your own site · 80×15
<a href="https://agentmods.dev/commands/danielpodolsky/ownyourcode/feature"><img src="https://agentmods.dev/badge/commands/danielpodolsky/ownyourcode/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.05611
Opus 5.5 $0.00004 $0.02244
Sonnet 5.5 $0.00002 $0.01122
Haiku 4.5 $0.00001 $0.00561

Measured 1mo ago against content hash 006c6821de35, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/own/feature.md · 524 lines

How it starts

The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/own:feature

⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (shift+tab). OwnYourCode commands don't work correctly with plan mode.

Create a feature specification using Spec-Driven Development (SDD).

Overview

This command follows the SDD workflow:

  1. AI generates the spec, design, and tasks for a phase based on minimal input
  2. Developer reviews them in the dashboard (the phase's Spec / Design / Tasks tabs)
  3. Developer adds any missing edge cases or requirements
  4. Then implementation begins with mentorship

Output (v2.5 — Dashboard SDD):

  • The detected roadmap-only phase in ownyourcode/dashboard/dashboard-data.js is advanced to specced — its spec, design, and tasks objects are written in place (replacing the phase's items[]). No spec.md/design.md/tasks.md files; everything lives in window.PROJECT, rendered by the dashboard's tabs.

Schema authority: ownyourcode/dashboard/DASHBOARD_CONTRACT.md defines the exact spec / design / tasks shapes and the mutation rules. Read it before writing. When this command's prose and the contract disagree, the contract wins.

Profile-Aware Behavior: Check .claude/ownyourcode-manifest.json for profile settings:

  • Junior profile → Collaborative spec creation (mandatory design involvement)
  • Other profiles with design_involvement=true → Collaborative spec creation
  • Profiles with design_involvement=false → AI generates, developer reviews

The SDD Philosophy

"Spec first, code second. But YOU own the judgment behind every line."

OwnYourCode uses SDD for planning, then builds with ownership — not by handing the junior a finished feature to read. How "build" works depends on profile:

  • Junior profile → Phase 6 runs the Implementation Loop: the junior predicts the judgment for each task before the AI reveals the code, then gets graded on the prediction. They own the code by being able to evaluate it, not by transcribing it.
  • Other profiles (v1) → the loop is not yet wired for them; SDD stops at the spec and implementation happens however that developer ships.

    Deliberate v1 scoping, not a permanent exclusion. The loop is built for the Junior profile first. Interview Prep is the strongest candidate to get it next — defending judgment in a live review is exactly what predict-before-reveal trains — with Career Switcher (rebuilding fundamentals) close behind. A future PR can extend Phase 6 to those profiles without contradicting this copy.

Read the full file on GitHub · 524 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 524 lines · 10 tokens per session scan A 006c6821de35

Subscribe to this mod's changes

feature is a command published in the GitHub repository DanielPodolsky/ownyourcode (292 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 5,611 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.