New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Feature

by yicheng47 in yicheng47/runner

Create, list, or manage feature specs and GitHub issues. An agent skill from yicheng47/runner.

MITAuto-check passedProduct & Project Management

Install Feature

skills CLI
$ npx skills add yicheng47/runner --skill feature -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yicheng47/runner feature --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yicheng47/runner.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/feature .claude/skills/feature && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feature
GitHub stars
273
Token cost
~1.1k tokens
SKILL.md length
626 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Create, list, or manage feature specs and GitHub issues. An agent skill from yicheng47/runner.

  • Works in 7 steps: Ask the user to describe the feature… → Assign the next available number by… → Create docs/features/{number}-{slug}.md… → …
  • Tasks that involve PRD writing
  • SKILL.md covers Usage, Labels, Priority and Conventions, plus 1 more section
  • Calls gh and git

What it does

Feature is an agent skill from yicheng47/runner. Create, list, or manage feature specs and GitHub issues

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with GitHub. The repository describes itself as: Where terminal agents work together. Claude Code, Codex, Copilot CLI and pi on the same task, in one mission, each keeping its own TUI in a real terminal. The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing

Example prompts

  • “/feature”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Ask the user to describe the feature (motivation, scope, key decisions).
  2. Assign the next available number by checking existing files in docs/features/.
  3. Create docs/features/{number}-{slug}.md with sections: Motivation, Scope, Implementation Phases, Verification.
  4. Pick a priority (see Priority below). If the user didn't state one, propose one and confirm before filing. Don't file unlabeled.
  5. Create a GitHub Issue with labels feature and the chosen P0/P1/P2/P3
  6. Update docs/features/README.md to include the new spec.
  7. Report the spec path, issue URL, and assigned priority.

What it can do on your machine

Read from SKILL.md and the folder at commit 0aef92a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature loads about 1.1k tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 626 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~16
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yicheng47/runner at commit 0aef92a, republished under its MIT licence (© yicheng47). 626 words, ~1,116 tokens.

Download SKILL.mdSave it as .claude/skills/feature/SKILL.md (or your agent's skills folder).
name
feature
description
Create, list, or manage feature specs and GitHub issues

Feature Management

Manage Runners' feature pipeline: specs live in docs/features/, tracking lives in GitHub Issues with the feature label.

Usage

/feature <action> [args]

Actions
new <name>

Create a new feature from scratch.

  1. Ask the user to describe the feature (motivation, scope, key decisions).
  2. Assign the next available number by checking existing files in docs/features/.
  3. Create docs/features/{number}-{slug}.md with sections: Motivation, Scope, Implementation Phases, Verification.
  4. Pick a priority (see Priority below). If the user didn't state one, propose one and confirm before filing. Don't file unlabeled.
  5. Create a GitHub Issue with labels feature and the chosen P0/P1/P2/P3:
    • Title: feat: <short description>
    • Body: Motivation, Scope summary, Implementation Phases, and a reference back to the spec file.
    • Command shape: gh issue create --label feature --label P1 --title "…" --body "…"
  6. Update docs/features/README.md to include the new spec.
  7. Report the spec path, issue URL, and assigned priority.
list

Show all features, sorted by priority.

  1. Fetch open features with priority + metadata as JSON so they can be sorted: gh issue list --label feature --state open --limit 50 --json number,title,labels,createdAt,assignees
  2. List all spec files in docs/features/ (excluding README).
  3. Sort the rows by priority (P0 first, then P1, P2, P3, then unlabeled-by-priority last). Within a priority bucket, sort by spec number ascending.
  4. Present a combined view: Priority, feature name, # (issue), spec file (if exists), Created. Issues without a P-label show — in priority and a callout asking the user to triage them.
  5. If the user asks for closed/shipped features too, repeat with --state all and add a State column.
close <issue-number>

Mark a feature as shipped.

  1. Close the GitHub Issue: gh issue close <number>
  2. If a matching spec file exists in docs/features/, move it to docs/features/archive/ with git mv. Shipped code is the source of truth, but the spec stays around as the "what we were going for" record (mirrors docs/impls/archive/).
  3. Update docs/features/README.md to drop the archived entry from the index.
prioritize <issue-number> <P0|P1|P2|P3>

Set or change the priority of an existing feature.

  1. Remove any existing P-label on the issue, then add the new one: gh issue edit <number> --remove-label P0 --remove-label P1 --remove-label P2 --remove-label P3 --add-label <priority> (Removing all four is safe — gh ignores remove-label for labels not present.)
  2. Confirm the new priority.
Show full SKILL.md (245 more words)Show less
spec <issue-number-or-name>

Open or create a spec for an existing feature issue.

  1. If a spec file already exists, show its path.
  2. If not, create one following the same format as new, pre-populated from the issue body.

Labels

  • feature — all feature issues use this label.
  • bug — for bug reports (not managed by this skill).
  • P0 / P1 / P2 / P3 — priority, exactly one per issue.

Priority

Every feature gets exactly one priority label. Rubric:

  • P0 — Required for the next ship; nothing else moves until this lands. Rare for features.
  • P1 — Wanted this cycle; blocks an active user workflow or has a stakeholder commitment.
  • P2 — Real product win, but no urgency. Pick up when the P1 queue is clear.
  • P3 — Idea / nice-to-have / "if we ever revisit X." OK to sit indefinitely; closing as wontfix later is fine.

When in doubt between two levels, pick the lower-urgency one and say why; over-labeling P0/P1 dilutes the signal.

Conventions

  • Spec files are numbered sequentially: 01-product-spec.md, 02-ai-quick-explain.md, etc.
  • Slugs are lowercase kebab-case derived from the feature name.
  • Specs for shipped features move to docs/features/archive/ — the implementation is the source of truth, but the spec stays as the "what we were going for" record (mirrors docs/impls/archive/).
  • The docs/features/README.md index only lists in-progress/planned specs.

Notes

  • Do not commit or push unless the user explicitly asks.
  • When creating issues, always include a reference to the spec file path in the issue body.
  • When creating specs, always include a reference to the GitHub issue URL.

© yicheng47, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/feature of yicheng47/runner.

Open the folder on GitHubat commit 0aef92a

Compare with similar skills

Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature this skillyicheng47/runner273—~1.1kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k1 repos~5.7kAutomated safety check: PassMIT
Creating Issuesopsmill/infrahub531—~1.2kAutomated safety check: PassApache-2.0
Feature SpecPackmindHub/packmind317—~1.8kAutomated safety check: PassApache-2.0
RalphTheCraigHewitt/skills157—~1kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

  • Creating Issues

    opsmill/infrahub

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

    531 GitHub stars~1.2k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Feature Spec

    PackmindHub/packmind

    Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description.

    317 GitHub stars~1.8k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Ralph

    TheCraigHewitt/skills

    Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation.

    157 GitHub stars~1k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed

  • To Issues

    smallnest/pigo

    Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

    475 GitHub stars~1.9k tokensUpdated 26 days ago
    Product & Project ManagementAuto-check passed

More from yicheng47/runner

  • Bug

    yicheng47/runner

    Report, list, or manage bug reports as GitHub issues. An agent skill from yicheng47/runner.

    273 GitHub stars~949 tokensUpdated yesterday
    Auto-check passed

  • Release

    yicheng47/runner

    Cut a Runner production release — bump the workspace version, tag vX.Y.Z, let release.yml build the draft for both platforms, write bilingual release notes (English, with 中文 collapsed in a details…

    273 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Nightly

    yicheng47/runner

    Cut or check Runner nightlies — one workflow for macOS and Windows, one public prerelease, shared stamp, and separate stable feeds

    273 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Feature

What does Feature do?

Create, list, or manage feature specs and GitHub issues. An agent skill from yicheng47/runner. Feature is an agent skill from yicheng47/runner.

When should I use Feature?

Feature fits situations like: tasks that involve PRD writing.

How do I install Feature in Claude Code?

Run `npx skills add yicheng47/runner --skill feature -a claude-code`. Or copy the skill folder (.agents/skills/feature in yicheng47/runner) into .claude/skills/feature in your project. Claude Code loads it when a task matches its description.

How do I install Feature in Codex?

Run `npx skills add yicheng47/runner --skill feature -a codex`. Or copy the skill folder (.agents/skills/feature in yicheng47/runner) into .agents/skills/feature in your project. Codex loads it when a task matches its description.

Can I use Feature in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yicheng47/runner --skill feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature, .gemini/skills/feature, .github/skills/feature and .opencode/skills/feature in your project.

What does Feature need to run?

Going by SKILL.md and its folder, Feature needs the command-line tools its instructions call (gh and git).

Does Feature access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Feature safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature use?

Feature is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Feature?

Skills that share tags, products or a category with Feature: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), Creating Issues (opsmill/infrahub, 531 stars) and Feature Spec (PackmindHub/packmind, 317 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature?

yicheng47 (a GitHub user) maintains it in yicheng47/runner, which has 273 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

Source: yicheng47/runner on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.