skills.rest
aspelldenny
aspelldennyCOMMUNITY
Explore all skills by this author →
GitHub

plan

Translate inbound requests into architect-level tickets with tasks and acceptance criteria.

Updated Apr 4, 2026
Search Tags:#workflow#architecture#handoff#plan#ticket#phiếu
One-click install
npx skills add https://github.com/aspelldenny/sos-kit --skill plan-aspelldenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/aspelldenny/sos-kit/tree/main/skills/attic/plan
Command: npx skills add https://github.com/aspelldenny/sos-kit --skill plan-aspelldenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps architects reliably translate inbound requests into well-scoped phiếu (tickets) for workers, ensuring architecture decisions are captured without code access and enabling smooth handoffs across roles.

Core Features & Use Cases

  • Structured phiếu generation: converts user requests into formal tickets with tasks, acceptance criteria, and verification anchors.
  • Role-aware guidance: enforces plan mode and documents constraints so Thợ can execute without ambiguity.
  • Handoff-ready outputs: links to relevant docs and precedents to speed up implementation.

Quick Start

Write a phiếu for the approved inbound request in docs/ticket format

Frequently Asked Questions about plan

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

FAQPage Schema
How do I translate an inbound request into structured architect tickets for handoffs?▼

To translate an inbound request into architect tickets, the skill converts requests into formal phiếu with deterministic task decomposition, acceptance criteria, and Task 0 verification anchors for traceable handoffs.

What is plan mode and how does it enforce constraints for worker execution?▼

Plan mode is a workflow state that enforces architecture constraints and documents decisions so Thợ can execute tasks without ambiguity, ensuring role-aware guidance and deterministic task decomposition across contexts.

Does this ticket generation workflow support both Claude Code and Claude Web?▼

Yes, the ticket generation workflow supports end-to-end phiếu planning in both Claude Code and Claude Web contexts, ensuring deterministic task decomposition and traceable handoffs across environments.

What's the best way to structure phiếu planning for smooth role handoffs?▼

The best way to structure phiếu planning is using standard docs/ticket templates as the authoritative output format, linking relevant precedents and enforcing verification anchors to speed up implementation.

Why do I need Task 0 verification anchors in my architecture tickets?▼

Task 0 verification anchors are needed to provide traceable handoffs, ensuring architecture decisions are captured accurately and workers can verify execution without ambiguity or code access.

Related Skills

Explore More Software Engineering Skills→
Sheldon-92Sheldon-92
3

tad-elicit

Automate structured requirement elicitation with 3-5 rounds of questioning and evidence recording.

Community
Intermediate
OmniNode-aiOmniNode-ai
3

insights-to-plan

Parse Claude Code insights HTML reports into prioritized design plans with acceptance criteria.

Official
Advanced
aspelldennyaspelldenny

verify

Grep Task 0 anchors against the codebase and generate a verification report.

Community
Intermediate
pradyumnasagarpradyumnasagar
6

nsf-standard

Create structured NSF Standard Research Proposals with templates and compliance checklists.

Community
Advanced