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 Boundary Planner

by BytePioneer-AI in BytePioneer-AI/codex-host

Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation.

LGPL-3.0Auto-check passedAgent Workflows

Install Feature Boundary Planner

skills CLI
$ npx skills add BytePioneer-AI/codex-host --skill feature-boundary-planner -a claude-code

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

GitHub CLI
$ gh skill install BytePioneer-AI/codex-host feature-boundary-planner --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/BytePioneer-AI/codex-host.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/feature-boundary-planner .claude/skills/feature-boundary-planner && 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-boundary-planner
GitHub stars
2.8k
Token cost
~755 tokens
SKILL.md length
333 words
Files
5 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
LGPL-3.0

At a glance

Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation.

  • Works in 5 steps: Use source discovery and the repository… → Classify the change as presentation,… → Trace each affected surface to its… → …
  • Impact analysis
  • SKILL.md covers Trace the current implementation and Plan and validate
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Boundary Planner is an agent skill from BytePioneer-AI/codex-host. Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation. Use for impact analysis, design planning, or implementation handoff.

Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/case-planning-template.md` and `references/impact-brief-template.md`).

It sits in Agent Workflows. The repository describes itself as: Run Pi and Claude Code directly in Codex Desktop. 在 Codex Desktop 中直接运行 Pi 和 Claude Code。 The licence is LGPL-3.0.

When your agent uses it

  • Impact analysis
  • Design planning
  • Implementation handoff

Example prompts

  • “/feature-boundary-planner”

Workflow steps

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

  1. Use source discovery and the repository documentation index to locate the relevant current contracts and entrypoints. Verify paths and…
  2. Classify the change as presentation, option source, draft/default, validation, command effect, persistence, or recovery.
  3. Trace each affected surface to its authoritative owner: Renderer/Desktop binding → Host request routing → Adapter/native operation →…
  4. Use $dep-refs for callers and re-exports. Imports alone do not prove a product dependency. Start with direct relationships, expanding when…
  5. Distinguish official Codex Threads from external Harness Threads; local and remote Hosts; Native Session facts from Host metadata…

What it can do on your machine

Read from SKILL.md and the folder at commit 08c7d65. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 Boundary Planner loads about 755 tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 333 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~755
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

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 BytePioneer-AI/codex-host at commit 08c7d65, republished under its LGPL-3.0 licence (© BytePioneer-AI). 333 words, ~755 tokens.

Download SKILL.mdSave it as .claude/skills/feature-boundary-planner/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
feature-boundary-planner
description
Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation. Use for impact analysis, design planning, or implementation handoff.
<!-- Adapted for codexhost from ZCode 872ad960de7ec172591f7e1952f7849229f94521. See ../NOTICE.md for provenance and licenses. -->

Feature boundary planner

Choose the scope implied by the request: impact-only reads and reports; planning establishes behavior and acceptance cases; implementation-handoff identifies concrete code and validation work. Respect existing user decisions and preserve unrelated work.

Trace the current implementation

  1. Use source discovery and the repository documentation index to locate the relevant current contracts and entrypoints. Verify paths and symbols in this checkout.
  2. Classify the change as presentation, option source, draft/default, validation, command effect, persistence, or recovery.
  3. Trace each affected surface to its authoritative owner: Renderer/Desktop binding → Host request routing → Adapter/native operation → confirmed event → projection. Some features end earlier; follow only the relevant path.
  4. Use $dep-refs for callers and re-exports. Imports alone do not prove a product dependency. Start with direct relationships, expanding when ownership or a caller remains unresolved.
  5. Distinguish official Codex Threads from external Harness Threads; local and remote Hosts; Native Session facts from Host metadata; capabilities from UI affordances. Use the repository terminology.

For stateful changes, show the event order and owner in a concise diagram. Identify cancellation, duplicate input, stale results, reconnect and recovery where they can affect behavior.

Plan and validate

In impact-only mode, report findings without changing implementation or specifications. In planning modes, maintain the relevant feature document for substantial behavior changes as required by AGENTS.md. Minor changes do not need a new documentation hierarchy.

Select representative high-risk cases rather than every combination of Harness, platform and state. Classify cases as accepted, undefined, pruned, ignored, or bug-candidate, giving evidence for exclusions. Use case planning for complex changes and impact brief for a structured handoff; fill only useful sections.

Inspect actual test files and package scripts before recommending commands. Distinguish planned coverage, existing tests, executed checks and runtime evidence. Missing source or a planned independent-client feature is not evidence of current capability.

Complete with the affected surfaces, owners, contracts, verified code references, native capability constraints, required checks and unresolved decisions. Ask only for decisions that cannot be resolved from authorized scope or current evidence.

© BytePioneer-AI, LGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/feature-boundary-planner of BytePioneer-AI/codex-host.

  • SKILL.md
  • agents/openai.yaml
  • references/case-planning-template.md
  • references/impact-brief-template.md
  • references/source-discovery.md

Open the folder on GitHubat commit 08c7d65

Compare with similar skills

Feature Boundary Planner 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 Boundary Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Boundary Planner this skillBytePioneer-AI/codex-host2.8k—~755Automated safety check: PassLGPL-3.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k36 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 36 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from BytePioneer-AI/codex-host

All 9 skills in this repo

  • Codexhost PR Triage

    BytePioneer-AI/codex-host

    手动增量分诊 codexhost Issue 与 PR，评估 PR 价值和实现克制，生成只读本地看板与回复草稿. An agent skill from BytePioneer-AI/codex-host.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Codexhost Add Harness

    BytePioneer-AI/codex-host

    为 codexhost 新增 Harness 插件，或规划、审查、补全现有 Harness Adapter。按当前公共契约实现原生能力，区分插件后端、预装发行和 Desktop 产品接入；不用于单纯添加 Model、Provider 或账号。

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Codexhost Release

    BytePioneer-AI/codex-host

    发布 codexhost 正式版、预览版，编写或确认 Release Notes，检查发布 CI，暂停、恢复或排查发布。支持正常正式发布，以及 npm latest + GitHub Prerelease、不给现有用户更新提示的预览发行。不用于普通代码提交或 Harness CLI 更新。

    2.8k GitHub stars~998 tokensUpdated yesterday
    Auto-check passed

  • Web Gui Tester

    BytePioneer-AI/codex-host

    Verify web frontend behavior through real GUI interactions, read-only page inspection, and screenshots.

    2.8k GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check passed

  • Codexhost Update Impact Audit

    BytePioneer-AI/codex-host

    Diagnose whether a Codex Desktop update changed codexhost Composer/CDP bindings, private Renderer DOM or React state, Host bridges, routing, the Codex usage submission gate, or injected UI.

    2.8k GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed

  • Control Browser

    BytePioneer-AI/codex-host

    Control a browser using the tools available in the current session to navigate, inspect, click, fill, capture and verify pages.

    2.8k GitHub stars~656 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Feature Boundary Planner

What does Feature Boundary Planner do?

Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation. Feature Boundary Planner is an agent skill from BytePioneer-AI/codex-host. Trace a codexhost feature change across UI surfaces, Host routing, Harness capabilities, state ownership, persistence, and validation.

When should I use Feature Boundary Planner?

Feature Boundary Planner fits situations like: impact analysis; design planning; implementation handoff.

How do I install Feature Boundary Planner in Claude Code?

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

How do I install Feature Boundary Planner in Codex?

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

Can I use Feature Boundary Planner 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 BytePioneer-AI/codex-host --skill feature-boundary-planner -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-boundary-planner, .gemini/skills/feature-boundary-planner, .github/skills/feature-boundary-planner and .opencode/skills/feature-boundary-planner in your project.

What does Feature Boundary Planner need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Boundary Planner is instructions for the agent only.

Does Feature Boundary Planner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feature Boundary Planner 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 Boundary Planner use?

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

How many tokens does Feature Boundary Planner use?

About 755 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Feature Boundary Planner?

Skills that share tags, products or a category with Feature Boundary Planner: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Boundary Planner?

BytePioneer-AI (a GitHub user) maintains it in BytePioneer-AI/codex-host, which has 2,791 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: BytePioneer-AI/codex-host on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.