feature-boundary-planner
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.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- 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.
02 资源文件 5
- 参考文档agents/openai.yaml280 B
- 参考文档references/case-planning-template.md3.5 KB
- 参考文档references/impact-brief-template.md5.2 KB
- 参考文档references/source-discovery.md3.6 KB
- 参考文档references/zcode-feature-graph.yaml21.5 KB
03 SKILL.md 正文
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
- 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.mdfor UI work andCONTEXT.mdfor plugin-store work. - Locate the entrypoint with
rg --filesand focusedrg -nsearches. Trace direct callers withpnpm 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. - Classify the change: presentation, option source, draft/default, validation, commit effect, persistence, or recovery.
- 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.
- 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.
- 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:
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.
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() || workspacePathfor isolation andworkspacePathfor execution/display. - Keep desktop
desktop-continuousdelivery separate from mobileweb-remote-replayablerecovery. - 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.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).