megaplan-tickets

Create repo-scoped Megaplan tickets as Markdown files linked to epics.

97|8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/peteromallet/arnold --skill megaplan-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: megaplan-tickets
Source: https://github.com/peteromallet/arnold/tree/main/megaplan/data/_codex_skills/megaplan-tickets
Command: npx skills add https://github.com/peteromallet/arnold --skill megaplan-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Megaplan tickets capture repo-scoped problems, bugs, and observations so they can be tracked as notes and automatically addressed when the resolving epic completes, preventing valuable findings from getting lost.

Core Features & Use Cases

  • Repo-scoped ticket files: Create inert ticket notes stored as committed Markdown files under <repo>/.megaplan/tickets/.
  • Ticket lifecycle management: List, show, search, edit, link to epics, and auto-flip tickets to addressed when linked epics complete.
  • Local or cloud-backed mirroring: Works as local-only via files, or mirrors to tickets/ticket_epics tables when a cloud store is configured.
  • Use case: During an epic, you notice an out-of-scope but important issue (like a recurring failure mode or missing validation); file it as a ticket so it can be routed into the right epic later.

Quick Start

Run: megaplan ticket new "Investigate timeout-related stderr loss in executor" -b "Observed stderr being swallowed when retries hit a timeout; verify logging path and retry handling." --tags observability,bug

Frequently Asked Questions about megaplan-tickets

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

FAQPage Schema
How do I track repo-scoped issues without blocking my current workflow?

Repo-scoped issue tracking captures non-blocking findings as Markdown notes under a repository directory, allowing you to file observations that can be routed and resolved later without interrupting execution.

Can I automatically close issue tickets when a related epic completes?

Yes, automatic ticket closure links issue notes to epics, flipping ticket status to addressed upon epic completion to prevent findings from getting lost during planning and execution workflows.

What's the best way to manage lightweight issue triage across multiple repositories?

Lightweight issue triage across multiple repos uses JSON-capable listing and search on repo-scoped ticket files, enabling status-driven filtering and cross-repo search for non-blocking observations.

Does this issue tracking approach work without a cloud database backend?

Yes, issue tracking works as local-only via committed Markdown files, or optionally mirrors to ticket and ticket_epics database tables when a cloud store is configured.

When do I need to file non-blocking observations as tickets during development?

File non-blocking observations as tickets when you notice out-of-scope but important issues during an epic, such as a recurring failure mode or missing validation, ensuring they are routed into the right epic later.

What limitations exist with auto-closing issue tickets linked to epics?

Auto-closing issue tickets requires root-level discovery metadata and support for linking behavior that resolves tickets upon epic completion, meaning incomplete or unlinked epics will not trigger automatic status flips.