ar-taskflow-planner

Plan large features into specs, tickets, and sequential PR-sized prompts.

1|2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-planner-mahsanamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ar-taskflow-planner
Source: https://github.com/mahsanamin/agentic-repos/tree/main/skills/ar-taskflow-planner
Command: npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-taskflow-planner-mahsanamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features that span multiple PRs often start without a written plan, leaving teams without a spec, a tracking ticket, or a clear breakdown of implementation tasks. This Skill turns a feature idea into a structured plan with issue-tracker tickets, an architecture spec, and ready-to-execute prompts. ## Core Features & Use Cases - Planning Ticket Creation: Immediately creates a planning ticket in Jira, GitHub Issues, or Linear so the team sees planning has started. - Spec and Decomposition: Guides an architecture discussion, writes a spec document with mermaid diagrams, and breaks it into sequential raw prompts that each produce one PR. - Story and Branch Setup: On approval, creates a Story ticket, a story branch for multi-PR integration, a machine-readable plan manifest, and TasksSummary log entries. - Use Case: You need to replace cron jobs with event-driven processing across several services. Run the planner to produce a spec, eight dependency-mapped prompts, a Jira Story, and a story branch, then execute each prompt as its own PR. ## Quick Start Say "plan feature" and describe the feature you want to plan, then follow the guided architecture discussion and approve the prompt breakdown.

Frequently Asked Questions about ar-taskflow-planner

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

FAQPage Schema
How do I plan a large feature that spans multiple PRs?▼

Run the planner with a brief feature description. It creates a planning ticket, guides an architecture discussion, writes a spec, and breaks the work into sequential raw prompts where each prompt becomes one PR targeting a shared story branch.

When should I use the feature planner instead of a single ticket creator?▼

Use the planner for large multi-PR features needing architecture discussion, a spec, and task decomposition. For a single PR-sized ticket like a bug fix or small task, use the fast-path ticket creator with no spec or branch setup.

Does the planner work with GitHub Issues or only Jira?▼

It is tracker-agnostic and supports Jira, GitHub Issues, Linear, or no tracker. The Jira path uses Epic and Story hierarchy with MCP transitions, while GitHub uses gh issue create with labels or milestones instead of hierarchy.

Can I resume or update an existing feature plan?▼

Yes. The planner checks for an existing plan_manifest.json and offers resume options: add more prompts, update the spec, view child task and PR status, or archive the plan once all prompts are completed.

What happens if the skill configuration file is missing?▼

The workflow stops and reports that configuration is missing, instructing you to run the initialization skill first. It reads paths and tracker settings from .claude/skill.config and .claude/config_hints.json before proceeding.