skills.rest
ianshank
ianshankCOMMUNITY
Explore all skills by this author →
GitHub

planning-handoff

Capture planning artifacts and generate structured handoff documents for DEV-SQE phases.

1|Updated Nov 28, 2025
Search Tags:#planning#architecture#documentation#adr#handoff#task-management#dev-sqe
One-click install
npx skills add https://github.com/ianshank/Platinum-Palladium-AI-Printing-Tool --skill planning-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-handoff
Source: https://github.com/ianshank/Platinum-Palladium-AI-Printing-Tool/tree/main/.claude/skills/planning-handoff
Command: npx skills add https://github.com/ianshank/Platinum-Palladium-AI-Printing-Tool --skill planning-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning teams often lose track of artifacts and decisions, leading to misalignment between planning and implementation.

Core Features & Use Cases

  • Capture task definitions, architectural decisions (ADRs), acceptance criteria, and dependency maps.
  • Generate handoff documents for downstream phases (DEV-SQE) and update persistent summaries.
  • Maintain a traceable ledger of planning activity and a structured state for resumption.

Quick Start

Gather planning artifacts from the current session and generate a formal handoff packet for DEV-SQE.

Frequently Asked Questions about planning-handoff

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

FAQPage Schema
How do I create a structured planning handoff for development and testing teams?▼

To create a structured planning handoff, you capture planning artifacts like task definitions and ADRs from your session to generate formal handoff documents for downstream DEV-SQE phases.

What is an append-only ledger in planning workflows and when do I need it?▼

An append-only ledger in planning workflows records task breakdowns and architectural decisions immutably. You need it to maintain traceable planning activity and ensure project alignment between phases.

How do I capture architectural decisions and acceptance criteria for a project handoff?▼

You capture architectural decisions and acceptance criteria by extracting them from your current planning session, updating persistent summaries and validating ledger integrity to create immutable handoff documents.

Can I update planning summaries and resume state across multiple handoff sessions?▼

Yes, you can update planning summaries and resume state across sessions. The workflow maintains a structured state and validates ledger integrity, enabling traceable resumption of planning activities.

What's the best way to maintain traceability for dependency maps during planning?▼

The best way to maintain traceability for dependency maps is using an append-only ledger that enforces immutable entries, ensuring dependency maps remain validated and aligned throughout the planning workflow.

Why does my planning handoff document fail validation before reaching downstream phases?▼

Planning handoff documents fail validation when ledger integrity checks detect missing or inconsistent entries. The workflow enforces append-only rules and validates criteria before creating immutable handoff packets.

Related Skills

Explore More Product & Management Skills→
pko89403pko89403
1

plan

Plan user specifications into ordered task lists with acceptance criteria.

Community
Intermediate
EremesNGEremesNG
1

plan-reviewer

Audit implementation plans for file existence and task clarity.

Community
Intermediate
ianshankianshank
1

dev-sqe-handoff

...

Community
Advanced
rezosndrezosnd

excel-generator

Generate styled Excel workbooks with formulas, charts, and data validation.

Community
Intermediate