What is feature-boundary-planner?

A planning tool for tracing a proposed behavior change through an existing codebase. It maps user-interface areas, state ownership, communication commands, saved data, and validation steps before implementation.

Use it for impact analysis, product-boundary planning, and implementation handoffs grounded in the checked-out repository.

It prevents feature plans from relying on obsolete files or guessed architecture. The result is limited to behavior supported by the current source or an explicit new requirement.

How ccbud/CCBuddy configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to ccbud/CCBuddy. 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/ccbud/CCBuddy/main/.agents/skills/feature-boundary-planner/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ccbud/CCBuddy

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ccbud/ccbuddy/feature-boundary-planner/github.svg)](https://agentmods.dev/skills/ccbud/ccbuddy/feature-boundary-planner)

Your own site

<a href="https://agentmods.dev/skills/ccbud/ccbuddy/feature-boundary-planner"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/feature-boundary-planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ccbud/ccbuddy/feature-boundary-planner"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/feature-boundary-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,304 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.

Model	Per session	Once invoked
Fable 5.1	$0.00089	$0.02304
Opus 5.5	$0.00036	$0.00922
Sonnet 5.5	$0.00018	$0.00461
Haiku 4.5	$0.00009	$0.00230

Measured 28d ago against content hash b5bb7232bc86, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-boundary-planner 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 28d 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.

.agents/skills/feature-boundary-planner/SKILL.md · 178 lines

How it starts

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

Feature Boundary Planner

Use this skill from the CCbuddy repository root before implementation when a request needs feature-impact discovery, product-boundary clarification, coverage planning, or an E2E handoff.

Treat impact discovery and boundary planning as two connected jobs:

Determine where the capability appears and what a change can affect.
Decide what the affected states should do and which combinations need coverage.

Do not begin with a large Cartesian product. Build a compact semantic impact map, verify it against live code, then ask only the questions that change the result.

Choose The Operating Mode

impact-only: Produce an Impact Brief. Do not change product code or existing product specs.
planning: Produce the Impact Brief, clarify product semantics, and update specs or planning documents before code.
implementation-handoff: Complete planning and prepare accepted cases for implementation or e2e-case-lifecycle.

Infer the least expansive mode from the user's request. A request to scan, explain, diagnose, or report impact is impact-only. A request to change or build uses planning unless the user explicitly limits the work.

Required Reading

For every impact scan, read:

docs/feature-impact-discovery.md
references/ccbuddy-feature-graph.yaml
references/impact-brief-template.md
the relevant rows in references/ccbuddy-domain-cross-products.md

For planning or implementation-handoff, also read:

packages/formal-proof/README.md
references/case-planning-template.md
the current feature spec, nearby case catalog, coverage matrix, decision worksheet, and testing workflow.

When conversation/session behavior is affected, read:

docs/conversation-protocol-declaration.md
docs/conversation-product-state-space.md
docs/conversation-session-case-catalog.md
docs/testing/conversation-session-e2e-coverage-matrix.md
docs/testing/conversation-session-e2e-development-workflow.md
docs/testing/conversation-session-requirement-matrix-workflow.md

Read the full file on GitHub · 178 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

28d ago Changed · +109 lines · +39 tokens per session b5bb7232bc86
1mo ago First seen · 69 lines · 50 tokens per session scan A 0e9c39feae1d

Subscribe to this mod's changes

feature-boundary-planner is a skill published in the GitHub repository ccbud/CCBuddy (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 2,304 once invoked, about $0.0004 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-09-25.

Claude Code Planning Project management chatgpt claude codex codex-cli grok

feature-boundary-planner next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-boundary-plannerccbud/CCBuddy	Skill	8	2d ago	Apache-2.0	A	89	Codex
search-docselie222/rakazo	Skill	8.0k	today	Apache-2.0	A	28	Claude Code, Codex
say-helloelie222/rakazo	Skill	8.0k	today	Apache-2.0	A	31	Claude Code, Codex
codex-auth-setupndycode/codex-multi-auth	Skill	566	7d ago	MIT	A	32	Claude Code, Codex
examplendycode/codex-multi-auth	Skill	566	7d ago	MIT	A	10	Claude Code, Codex
explain-codebasesuryast/free-ai-agent-skills	Skill	2	19d ago	MIT	A	58	Claude Code, Codex
context-canvas-reflectionphenomenoner/Chatgpt-Codex-App-Plus	Skill	2	16d ago	MIT	A	99	Codex

CCBuddy: Skill for Codex