SkillsAdd

smithery/kieutrongthien

plan-agile-planning

Create epics, user stories, and estimate points for predictable delivery.

Installation

$ npx skills add smithery/kieutrongthien --skill plan-agile-planning
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery/kieutrongthien.

npx skills add smithery/kieutrongthien
backend-golang 0

Browse all from smithery/kieutrongthien

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,893 B
  • docs SUMMARY.md 100 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Agile Planning Skill

What it does

  • Translates new requirements into epics and user stories mapped to the active project.
  • Defines acceptance criteria and estimation (story points/t-shirt sizes) consistent with team velocity.
  • Produces a prioritized backlog aligned to outcomes and logs decisions in memory.

When to use

  • Before starting a new initiative or feature set.
  • When backlog is unclear or lacks acceptance criteria or estimates.
  • When stakeholders need scope clarity and effort signals.

Key operations

  • Identify active project (projects/current-project.txt or PROJECT.md status) and review PROJECT.md, backlog/epics.json, backlog/user-stories.json, current-sprint.json.
  • Identify outcomes and slice into epics and stories with INVEST acceptance criteria.
  • Estimate effort (points) and dependencies; flag risks/assumptions; check against historical velocity in sprint-history.md.
  • Prioritize using value vs. effort and constraints; propose sprint placement respecting capacity guidance from AGENTS.md.
  • Log rationale and decisions in memory/YYYY-MM-DD.md.

Output files

  • projects/<ACTIVE>/backlog/epics.json — epics with goals, scope, risks, dependencies.
  • projects/<ACTIVE>/backlog/user-stories.json — prioritized user stories with acceptance criteria and estimates.
  • projects/<ACTIVE>/backlog/backlog-index.md — human-readable summary.
  • projects/<ACTIVE>/backlog/assumptions-risks.md — assumptions, constraints, risks, mitigations.
  • projects/<ACTIVE>/backlog/estimation-log.md — estimation rationale and calibration notes.
  • memory/YYYY-MM-DD.md — decisions, rationale, sprint placement notes.

Example workflow

  1. Run session init (AGENTS.md checklist); confirm active project.
  2. Capture product goal and constraints; scan backlog for overlaps.
  3. Draft epics and slice into stories with acceptance criteria.
  4. Estimate each story (points); note dependencies and risks; check velocity.
  5. Prioritize, propose sprint placement, update backlog files; log decisions in memory/YYYY-MM-DD.md.

Best practices

  • Make stories INVEST and testable; acceptance criteria are observable.
  • Calibrate points with recent completed stories; avoid single-person estimates.
  • Keep epics outcome-oriented; avoid solution-locking too early.
  • Note risks and unknowns explicitly; create spikes for research.
  • Respect capacity guidance: planned points ≤ velocity × 1.1 and reserve 10–20% buffer.

Related resources

  • AGENTS.md (session flow, safety rules)
  • SKILLS.md, MEMORY.md, memory/YYYY-MM-DD.md
  • projects/<ACTIVE>/PROJECT.md, backlog/epics.json, backlog/user-stories.json, backlog/backlog-index.md
  • Definition of Ready/Done; team estimation guide (Planning Poker)