plan

Synthesize Jujutsu commit history into structured org-mode project roadmaps.

Updated Nov 7, 2024
One-click install
npx skills add https://github.com/patmaddox/lab --skill plan-patmaddox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/patmaddox/lab/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/patmaddox/lab --skill plan-patmaddox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented project tracking by automatically synthesizing commit history into a coherent, actionable org-mode plan.

Core Features & Use Cases

  • Automated Synthesis: Reads commit messages from a Jujutsu (jj) revset to generate a structured project roadmap.
  • Interactive Feedback: Supports inline CR (comment/reply) blocks, allowing users to provide feedback directly within the generated plan.
  • Context Preservation: Maintains a persistent questions section to track open loops and user-model collaboration without losing historical context.

Quick Start

Trigger the plan skill by typing /plan followed by your desired revset and output filename to generate your project roadmap.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn commit messages into a structured org-mode project plan?

You can turn commit messages into a structured org-mode project plan by synthesizing Jujutsu version control revsets to identify work-in-progress and generate actionable project roadmaps. The skill parses commit descriptions to maintain document state across iterations.

What is the best way to track fragmented project history using Jujutsu?

Tracking fragmented project history with Jujutsu is best handled by automatically synthesizing commit history into a coherent, actionable org-mode plan. This approach preserves context and maintains a persistent questions section to track open loops.

Does generating an org-mode roadmap require a specific version control tool?

Generating an org-mode roadmap requires integration with the jj command-line tool. It operates specifically on Jujutsu version control revsets to parse commit descriptions and identify work-in-progress for the documentation.

How do I provide feedback on an automatically generated project plan?

You provide feedback on an automatically generated project plan by using inline CR (comment/reply) blocks directly within the plan. This interactive feature allows user-model collaboration without losing historical context across iterations.

Can I maintain context for open loops when generating task documentation?

You can maintain context for open loops when generating task documentation because the skill maintains a persistent questions section. This tracks open loops and supports user-model collaboration without losing historical context during iterations.

What are the limitations of synthesizing commit history into org-mode files?

A limitation of synthesizing commit history into org-mode files is the strict dependency on the jj command-line tool to parse revsets. Without Jujutsu commit descriptions, the automated project roadmap generation cannot operate.