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 zai-org in zai-org/ZCode

Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation.

Apache-2.0Auto-check passed

Install Feature Boundary Planner

skills CLI
$ npx skills add zai-org/ZCode --skill feature-boundary-planner -a claude-code

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

GitHub CLI
$ gh skill install zai-org/ZCode 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/zai-org/ZCode.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
7.6k
Token cost
~1.4k tokens
SKILL.md length
699 words
Files
6 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation.

  • Works in 6 steps: Search aliases and node IDs in… → Locate the entrypoint with rg --files… → Classify the change: presentation,… → …
  • Impact analysis
  • SKILL.md covers Choose The Scope, Find Current Evidence, Maintain The Seed Graph and Plan And Prune, plus 2 more sections
  • Calls rg and pnpm

What it does

Feature Boundary Planner is an agent skill from zai-org/ZCode. Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

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

The repository describes itself as: Z.ai's coding agent harness. Powerful, intelligent, extensible. The licence is Apache-2.0.

When your agent uses it

  • Impact analysis
  • Product-boundary planning
  • An implementation handoff grounded in the checked-out source

Example prompts

  • “/feature-boundary-planner”

Workflow steps

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

  1. Search aliases and node IDs in zcode-feature-graph.yaml for the user's terms. Read only matched nodes and their one-hop relationships…
  2. Locate the entrypoint with rg --files and focused rg -n searches. Trace direct callers with pnpm dep:refs : when the symbol is a…
  3. Classify the change: presentation, option source, draft/default, validation, commit effect, persistence, or recovery.
  4. Trace each user surface separately through validation and the command that commits the change. Shared UI components do not establish…
  5. Identify the authoritative owner, derived views, protocol boundary, persistence and failure behavior. Name the semantic reason for each…
  6. Inspect one meaningful semantic hop first, expanding only when an unresolved owner or caller requires it. Rank relationships as…

What it can do on your machine

Read from SKILL.md and the folder at commit 29628c9. 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:

    • rg
    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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 Boundary Planner loads about 1.4k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 699 words of instructions outside code blocks.

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

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 zai-org/ZCode at commit 29628c9, republished under its Apache-2.0 licence (© zai-org). 699 words, ~1,444 tokens.

Download SKILL.mdSave it as .claude/skills/feature-boundary-planner/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
feature-boundary-planner
description
Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

Feature Boundary Planner

Trace the requested behavior through the current checkout. A feature belongs in the result only when current source or an explicit new requirement supports it. Verify referenced paths and symbols before using them; do not reconstruct removed functionality from historical catalogs.

Choose The Scope

  • impact-only: inspect and report without changing code or product specs.
  • planning: establish behavior and acceptance cases before implementation.
  • implementation-handoff: turn confirmed decisions into a bounded implementation and validation plan.

Use the mode implied by the request. Clarify only unknown decisions that materially change the scope; do not ask the user to reconfirm facts already established in this task.

Find Current Evidence

  1. Search aliases and node IDs in zcode-feature-graph.yaml for the user's terms. Read only matched nodes and their one-hop relationships, then verify the declared files, symbols and semantics against the current checkout. The graph is a curated seed index, not a complete feature inventory. Use source-discovery.md to fill gaps or start when there is no match. Read the relevant existing contracts and package scripts; read DESIGN.md for UI work and CONTEXT.md for plugin-store work.
  2. Locate the entrypoint with rg --files and focused rg -n searches. Trace direct callers with pnpm dep:refs <file>:<symbol> when the symbol is a TypeScript export. If an indexed codegraph tool is available, use it as additional evidence and verify its paths against the checkout.
  3. Classify the change: presentation, option source, draft/default, validation, commit effect, persistence, or recovery.
  4. Trace each user surface separately through validation and the command that commits the change. Shared UI components do not establish shared state or side effects.
  5. Identify the authoritative owner, derived views, protocol boundary, persistence and failure behavior. Name the semantic reason for each upstream or downstream dependency; imports alone do not prove a product relationship.
  6. Inspect one meaningful semantic hop first, expanding only when an unresolved owner or caller requires it. Rank relationships as must-inspect, should-inspect, conditional, invariant-only, or evidence-only.

For stateful or asynchronous behavior, show a concise diagram:

text
user action → surface draft → validation → owner command → event / persistence
                                                └── derived UI projection

Maintain The Seed Graph

Keep existing node IDs for unchanged semantic boundaries and add aliases for new terminology. Report missing seeds or changed relationships as graph-drift-candidate; static reachability alone does not establish a product dependency.

In impact-only mode, report proposed graph changes without editing files. In planning or implementation, update only verified entries within the task's scope. Follow the graph contract: check YAML parsing, unique IDs, relationship endpoints and ranks, and tracked source paths and symbols. Do not restore missing historical docs or claim test coverage from a graph entry.

Show full SKILL.md (276 more words)Show less

Plan And Prune

In planning modes, write or update a feature spec before implementation. Create the spec directory if needed; do not assume an existing case catalog, test runner, or coverage workflow.

Select only dimensions that can change behavior: state, event, target, client mode, delivery kind, workspace identity, runtime availability and persistence source. Prefer representative and high-risk combinations over a global Cartesian product.

Classify cases as accepted, undefined, pruned, ignored, or bug-candidate. Give every pruned case an invariant or guard; leave undefined behavior as a concrete decision. Record accepted cases with setup, action, assertions and required evidence using case-planning-template.md.

Before handing off validation, check which tests, fixtures and commands actually exist in the target package. Distinguish planned tests, executed tests and admitted regression coverage. A missing test path is a gap, not coverage.

Output

Use impact-brief-template.md for the relevant parts of the result:

  • behavior summary and scope;
  • UI surface matrix, shared implementation and divergent behavior;
  • ranked dependencies with current file/symbol evidence;
  • state owners, validation points, commit commands and persistence;
  • invariants and representative validation cases;
  • unresolved decisions, unavailable evidence and relevant graph drift or updates.

Boundaries

  • Preserve workspaceIdentity?.trim() || workspacePath for isolation and workspacePath for execution/display.
  • Keep desktop desktop-continuous delivery separate from mobile web-remote-replayable recovery.
  • Trace accepted commands to their authoritative owner; do not turn a client draft or optimistic overlay into another accepted queue.
  • Treat runtime state, snapshots, indexes, settings and caches as distinct until their synchronization is proven.
  • Do not infer current functionality from a directory left behind by build artifacts, an old document, or a historical branch.
  • Do not silently change product semantics to match an implementation discrepancy; report the evidence and the decision needed.

© zai-org, Apache-2.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 5 other files (references) in .agents/skills/feature-boundary-planner of zai-org/ZCode.

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

Open the folder on GitHubat commit 29628c9

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 skillzai-org/ZCode7.6k—~1.4kAutomated safety check: PassApache-2.0
Plannerpenpot/penpot61k—~2.7kAutomated safety check: PassMPL-2.0
Feature Boundary PlannerBytePioneer-AI/codex-host2.8k—~755Automated safety check: PassLGPL-3.0
Attack Surface Mappingyaklang/hack-skills2.4k—~2.6kAutomated safety check: PassMIT
Feature Maponyx-dot-app/onyx32k—~459Automated safety check: PassCustom licence
Token Mapnexu-io/open-design100k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Planner

    penpot/penpot

    Read-only planning and architecture analysis — produce a structured implementation plan with task breakdown, acceptance criteria, sizing, and checkpoints.

    61k GitHub stars~2.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Feature Boundary Planner

    BytePioneer-AI/codex-host

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

    2.8k GitHub stars~755 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Attack Surface Mapping

    yaklang/hack-skills

    Draw a testable attack surface from one authorized target URL or one application.

    2.4k GitHub stars~2.6k tokensUpdated 25 days ago
    SecurityAuto-check passed

  • Feature Map

    onyx-dot-app/onyx

    Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break.

    32k GitHub stars~459 tokensUpdated today
    Auto-check passed

  • Token Map

    nexu-io/open-design

    Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.

    100k GitHub stars~1.4k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Agent Planner

    ruvnet/ruflo

    Agent skill for planner - invoke with $agent-planner. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

More from zai-org/ZCode

  • Architecture Governance

    zai-org/ZCode

    Apply the repository's architecture policy to code changes by generating a bounded context package, checking module and layer boundaries, and reporting baseline-aware violations.

    7.6k GitHub stars~1.2k tokensUpdated 10 days ago
    Auto-check passed

  • Control Browser

    zai-org/ZCode

    A skill your agent uses when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside…

    7.6k GitHub stars~4.6k tokensUpdated 10 days ago
    Auto-check passed

  • Dep Refs

    zai-org/ZCode

    A skill your agent uses when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who…

    7.6k GitHub stars~552 tokensUpdated 10 days ago
    Auto-check passed

  • Dynamic Workflows

    zai-org/ZCode

    A skill your agent uses when writing, debugging, or resubmitting a dynamic-workflow script for the CreateWorkflow tool: choosing subagent topology, typing subagent results, fanning out over files or…

    7.6k GitHub stars~23k tokensUpdated 10 days ago
    Auto-check passed

Questions about Feature Boundary Planner

What does Feature Boundary Planner do?

Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Feature Boundary Planner is an agent skill from zai-org/ZCode. Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation.

When should I use Feature Boundary Planner?

Feature Boundary Planner fits situations like: impact analysis; product-boundary planning; an implementation handoff grounded in the checked-out source.

How do I install Feature Boundary Planner in Claude Code?

Run `npx skills add zai-org/ZCode --skill feature-boundary-planner -a claude-code`. Or copy the skill folder (.agents/skills/feature-boundary-planner in zai-org/ZCode) 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 zai-org/ZCode --skill feature-boundary-planner -a codex`. Or copy the skill folder (.agents/skills/feature-boundary-planner in zai-org/ZCode) 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 zai-org/ZCode --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?

Going by SKILL.md and its folder, Feature Boundary Planner needs the command-line tools its instructions call (rg and pnpm).

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 Apache-2.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 1.4k tokens (SKILL.md is roughly 5.8k 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 8.6k 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: Planner (penpot/penpot, 61k stars), Feature Boundary Planner (BytePioneer-AI/codex-host, 2.8k stars), Attack Surface Mapping (yaklang/hack-skills, 2.4k stars) and Feature Map (onyx-dot-app/onyx, 32k 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?

zai-org (a GitHub organization) maintains it in zai-org/ZCode, which has 7,572 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 29, 2026.

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