Run any Skill in Manus with one click

plan-tickets

Stars0

Forks1

UpdatedJuly 24, 2026 at 02:55

Draft and classify structured tickets with area prefixes and five-section format (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes), plus a readiness checklist. Draft-only by default; create issues only after explicit user approval. Use when breaking a plan into tickets, creating Jira/GitHub issues, classifying work items.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

igmarin

igmarin/agnostic-planning-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

3 files

SKILL.md

readonly

name	plan-tickets
type	atomic
license	MIT
description	Draft and classify structured tickets with area prefixes and five-section format (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes), plus a readiness checklist. Draft-only by default; create issues only after explicit user approval. Use when breaking a plan into tickets, creating Jira/GitHub issues, classifying work items.
metadata	{"version":"1.0.0","user-invocable":"true"}

Plan Tickets

Normalize inputs, classify each work item, draft tickets in a standard structure. Default mode: draft-only.

HARD-GATE

Do not create tracker issues unless explicitly asked.
Do not assume tracker credentials, project fields, sprint IDs, or status behavior.
If only tickets are requested, return Markdown drafts.

Core Process

Normalize initiative: theme, project, draft vs. create mode, default bucket, constraints.
Classify each ticket: type, area, execution order, dependency level, target bucket using the classification rules below.
Apply sprint placement: foundation/api before client, exclude external confirmations, place follow-up tickets in ready-to-refine.
Apply title prefixes: BE | (backend), FE | (frontend), Mobile | (mobile).
Draft each ticket with five sections: Summary, Background, Acceptance Criteria, Dependencies, Technical Notes.
Output:

Draft-only (default): Markdown tickets with classification line and five-section structure plus a readiness checklist.

Create-in-tracker: After explicit approval, create issues using the tracker API. Validate required fields; do not set status on create. Confirm with one issue before bulk creation.

Classification Rules

Optional: coordination_need, external_dependency, urgency.

Extended Resources

EXAMPLES.md — full plan-to-ticket example
assets/ticket-samples/sample_issue.md — sample issue format

Integration

Skill	When
generate-tasks	After tasks exist
create-prd	Align tickets with PRD scope

More from this repository

same repository

agnostic-planning-skills

igmarin/agnostic-planning-skills

Master orchestrator for the Agnostic Planning Skills library. Use to discover and activate 11 language-agnostic skills and 4 personas for product planning, task breakdown, estimation, risk assessment, ticket generation, backlog prioritization, sprint planning, retrospectives, requirements clarification, GitHub issue management, and status reporting. Personas guide end-to-end workflows. prd, planning, tasks, tickets, estimation, risks, status, backlog, sprint, retrospective, tdd, agile, product management, requirements, clarification.

2026-07-240

identify-risks

igmarin/agnostic-planning-skills

Scan dependency chains, single points of failure, ambiguous requirements, external dependencies, capacity, and technical uncertainty. Every risk must reference a specific task/requirement as evidence. Output a risk register with likelihood, impact, and mitigations. Use for risk assessment, what could go wrong, risk register.

2026-07-240

prioritize-backlog

igmarin/agnostic-planning-skills

Prioritize a backlog using RICE, MoSCoW, value-vs-effort, or WSJF. Rank items by impact and urgency, produce ordered backlog with scores and rationale. Use when prioritizing a backlog, ranking features, applying frameworks.

2026-07-240

generate-status-report

igmarin/agnostic-planning-skills

Generate a stakeholder status report from task data — never fabricate progress, mark unknowns as "needs update". Includes Executive Summary (health, key accomplishment, top concern) and standard sections. Use for status report, sprint update, weekly update, project status.

2026-07-240

github-issue

igmarin/agnostic-planning-skills

Use to create, track, or manage GitHub issues with automatic project board integration (V2 and Classic), milestone tracking, and stage lifecycle (todo → in-progress → in-review → done). Covers issue creation, status updates, project board moves, and completion workflows.

2026-07-240

create-prd

igmarin/agnostic-planning-skills

Draft a clear actionable PRD from a feature — focus on what/why, no code, save to /tasks/prd-SLUG.md. Use when the user wants a PRD, product requirements, plan a feature, write a spec.

2026-07-240

name	plan-tickets
type	atomic
license	MIT
description	Draft and classify structured tickets with area prefixes and five-section format (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes), plus a readiness checklist. Draft-only by default; create issues only after explicit user approval. Use when breaking a plan into tickets, creating Jira/GitHub issues, classifying work items.
metadata	{"version":"1.0.0","user-invocable":"true"}

Plan Tickets

Normalize inputs, classify each work item, draft tickets in a standard structure. Default mode: draft-only.

HARD-GATE

Do not create tracker issues unless explicitly asked.
Do not assume tracker credentials, project fields, sprint IDs, or status behavior.
If only tickets are requested, return Markdown drafts.

Core Process

Normalize initiative: theme, project, draft vs. create mode, default bucket, constraints.
Classify each ticket: type, area, execution order, dependency level, target bucket using the classification rules below.
Apply sprint placement: foundation/api before client, exclude external confirmations, place follow-up tickets in ready-to-refine.
Apply title prefixes: BE | (backend), FE | (frontend), Mobile | (mobile).
Draft each ticket with five sections: Summary, Background, Acceptance Criteria, Dependencies, Technical Notes.
Output:

Draft-only (default): Markdown tickets with classification line and five-section structure plus a readiness checklist.

Create-in-tracker: After explicit approval, create issues using the tracker API. Validate required fields; do not set status on create. Confirm with one issue before bulk creation.

Classification Rules

Optional: coordination_need, external_dependency, urgency.

Extended Resources

EXAMPLES.md — full plan-to-ticket example
assets/ticket-samples/sample_issue.md — sample issue format

Integration

Skill	When
generate-tasks	After tasks exist
create-prd	Align tickets with PRD scope