arvindrk - Read
agent/vision.md(if present),agent/categories.json(if present),agent/feature_list.json,agent/PROGRESS.md, and recent commits. - Identify unblocked tasks by
depends_on,status, andpasses. - For lookahead: consider current horizon (via Ruflo memory or agent/harness/horizon if present), align to vision goals, score for category balance per weights.
- Prefer tasks that advance vision while respecting approximate category distribution over the slice/recent runs. Fall back to small high-confidence improvements in reliability, observability, DX, or evals when no vision.
- Update
feature_list.jsononly for durable task state changes. Record category if set. - Append the rationale (vision link + category consideration) and next action to
agent/PROGRESS.md. - If implementation is next, route to a single writer in a dedicated branch or worktree.
Feature Planning
Generic planner for feature work using agent/feature_list.json + vision/categories. Use after merges, roadmap changes, or failed verification. Load project vision.md and categories.json for direction and balance.
Feature Planning by arvindrk · af34526
npx skillmds@latest add arvindrk/feature-planning File contents
---name: feature-planningdescription: Generic planner for feature work using agent/feature_list.json + vision/categories. Use after merges, roadmap changes, or failed verification. Load project vision.md and categories.json for direction and balance.---1. Read `agent/vision.md` (if present), `agent/categories.json` (if present), `agent/feature_list.json`, `agent/PROGRESS.md`, and recent commits.2. Identify unblocked tasks by `depends_on`, `status`, and `passes`.3. For lookahead: consider current horizon (via Ruflo memory or agent/harness/horizon if present), align to vision goals, score for category balance per weights.4. Prefer tasks that advance vision while respecting approximate category distribution over the slice/recent runs. Fall back to small high-confidence improvements in reliability, observability, DX, or evals when no vision.5. Update `feature_list.json` only for durable task state changes. Record category if set.6. Append the rationale (vision link + category consideration) and next action to `agent/PROGRESS.md`.7. If implementation is next, route to a single writer in a dedicated branch or worktree.
arvindrk/ycagent.ai/tree/main/.agents/skills/feature-planning commit af3452636e
Frequently asked questions
Run npx skillmds@latest add arvindrk/feature-planning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Generic planner for feature work using agent/feature_list.json + vision/categories. Use after merges, roadmap changes, or failed verification. Load project vision.md and categories.json for direction and balance. It is listed under Product & Planning on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
arvindrk (@arvindrk) published this skill. Their other Agent Skills are listed on their SkillMD profile.