skills.rest
LaPaGaYo
LaPaGaYoCOMMUNITY
Explore all skills by this author →
GitHub

plan

Convert upstream framing into bounded tasks with acceptance criteria and verification commands.

1|Updated Mar 31, 2026
Search Tags:#planning#lifecycle#sprint#task-decomposition#nexus#execution-readiness
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill plan-lapagayo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/plan
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill plan-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical Nexus planning turns high-level framing into concrete, executable tasks with measurable criteria and a verifiable plan.

Core Features & Use Cases

  • Break framing into bite-sized tasks with observable criteria and a defined verification command.
  • Produce sprint-contract artifacts that guide downstream /build, /review, and /handoff.
  • Support governance-aware planning by embedding risk and decision rationales into the contract.

Quick Start

Run the /plan command to translate your framing into a sprint-ready contract.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I decompose high-level project framing into execution-ready sprint tasks?▼

Sprint planning translates framed requirements into bounded tasks with observable acceptance criteria and defined verification commands. This produces sprint contracts that measure execution readiness and guide downstream build, review, and handoff phases.

What is a sprint contract and how does it support task-level decomposition?▼

A sprint contract is an artifact generated during task decomposition that embeds risk and decision rationales into verifiable task definitions. It guides downstream build, review, and handoff phases by ensuring tasks have observable acceptance criteria and defined verification commands.

Can I embed governance and risk rationales directly into my sprint plan?▼

Yes, governance-aware planning embeds risk and decision rationales directly into the sprint contract during task decomposition. This ensures execution-ready plans maintain traceability while producing bounded tasks with observable acceptance criteria.

How do I ensure my sprint tasks are verifiable and execution-ready?▼

Execution-ready sprint tasks must be bounded to three sentences or less, feature observable acceptance criteria, and include a defined verification command. This structured task decomposition ensures downstream builds and reviews can verify completion objectively.

What is the best way to translate upstream framing into a sprint-ready plan?▼

Canonical Nexus planning translates upstream framing into concrete, executable tasks with measurable criteria and verifiable plans. Applying task decomposition ensures each item is bounded, observable, and includes a defined verification command for execution readiness.

Does sprint scoping work without prior framing or task-level decomposition?▼

No, sprint scoping requires upstream framing to perform effective task-level decomposition. Without framed requirements, the planning process cannot generate bounded tasks with observable acceptance criteria and defined verification commands needed for execution readiness.

Related Skills

Explore More Product & Management Skills→
wunkiwunki
19

create-plan

Interview stakeholders and generate a structured PLAN.md for coding tasks.

Community
Advanced
thompson0012thompson0012
28

generator-execution

Execute a contract-bound sprint and produce runtime.md and handoff.md artifacts.

Community
Advanced
AP3X-DevAP3X-Dev
9

sprint-planning

Plan two-week sprint cycles with realignment loops and governance checks.

Community
Advanced
vuthuonghai-stevevuthuonghai-steve
1

task-planner

Decompose requirements documents into phases, tasks, and subtasks.

Community
Intermediate