| name | agent-ui-feature-planning |
| description | Plan Agent UI repository features before implementation. Use when the user asks to make a feature plan, plan before coding, research/plan/todo/goal prompt, solve a problem group, architecture plan, 実装前に計画, feature planning, PLAN/TODO作成, or goal-prompt generation for this repo. Do not use for small direct edits, review-only requests, npm release operations, upstream sync, browser QA, or external host-app integration unless the user explicitly asks for a planning package. |
Agent UI Feature Planning
Use this skill to create a repo-specific planning package before implementation.
Do not implement the feature. Produce artifacts only under:
.agent-work/features/<date>-<slug>/
research.md
plan.md
todo.md
goal-prompt.md
Do not create root-level aliases unless the user explicitly asks.
First Pass
- Read freshness policy, then read
references/freshness-manifest.json.
- Run
node .agents/skills/agent-ui-feature-planning/scripts/check-freshness.mjs
from the repo root when script execution is available. If watched inputs
changed, do targeted refresh before planning; do full refresh only for
structural repo, CI, build, or agent-guidance changes, or when the user asks.
Record the result in research.md.
- Read artifact contract and
review rubric.
- Read repo research summary, then
inspect the current repo files it references before finalizing the plan.
- Choose a concise slug from the user's requested feature or problem group.
- Create or switch to the single branch that will carry both planning and
implementation before writing artifacts.
- Create the canonical artifact directory with today's date:
.agent-work/features/<YYYY-MM-DD>-<slug>/.