skills.rest
hdtinh57
hdtinh57COMMUNITY
Explore all skills by this author →
GitHub

planning

Coordinate backlog planning and architecture decisions across product and technical domains.

1|Updated Apr 23, 2026
Search Tags:#planning#architecture#adr#governance#backlog#sprint#task-decomposition
One-click install
npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill planning-hdtinh57
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/hdtinh57/codex-orchestrated-project-template/tree/main/.codex/skills/planning
Command: npx skills add https://github.com/hdtinh57/codex-orchestrated-project-template --skill planning-hdtinh57

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and architecture work are often fragmented across teams and documents. This skill provides a structured approach to backlog management, sprint planning, feature decomposition, and ADR-driven design decisions.

Core Features & Use Cases

  • Backlog management, sprint planning, task decomposition, and dependency tracking.
  • ADR drafting, architecture decision support, and governance for system design.
  • Risk-aware planning with guardrails, DoD criteria, and sprint health signals.

Quick Start

Start planning your next sprint by outlining goals, decomposing features into tasks, and drafting ADRs for upcoming architecture decisions.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure backlog management and sprint planning for cross-functional teams?▼

Backlog management and sprint planning are structured by coordinating feature decomposition, dependency mapping, and task templates to align teams. This approach provides sprint health signals and risk tracking to ensure aligned execution across product and technical domains.

What is an ADR and when do I need architecture governance for system design?▼

An ADR, or Architecture Decision Record, captures design decisions to provide governance for system design. You need architecture governance when coordinating complex technical domains to ensure structured, risk-aware design decisions align with overall product goals.

How do I decompose features into trackable tasks with dependency mapping?▼

Feature decomposition into trackable tasks uses structured templates to break down requirements while applying dependency mapping. This coordinates task execution and provides risk tracking guardrails to maintain sprint health and alignment.

Can I apply guardrails and Definition of Done criteria to risk-aware planning?▼

Yes, risk-aware planning applies explicit guardrails and Definition of Done criteria to coordinate architecture decisions and backlog management. This ensures structured task templates meet required quality standards before sprint completion.

What is the best way to align product and technical domains during sprint planning?▼

The best way to align product and technical domains during sprint planning is coordinating architecture decisions and backlog management together. Applying ADR drafting, task decomposition, and dependency mapping ensures both domains remain synchronized.

Related Skills

Explore More Product & Management Skills→
AirMileAirMile

dev-define

Define feature requirements and architecture from project backlog and plans.

Community
Advanced
warpcodewarpcode
2

pm-project-analyser

Break down project concepts into epics and plan sprints by capacity.

Community
Intermediate
script-reposcript-repo

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning via AI swarm coordination.

Community
Advanced
aibangjuxinaibangjuxin
2

sprint-prioritizer

Prioritize product backlogs using RICE and MoSCoW frameworks.

Community
Intermediate