planwithme

Generate PLAN.md, CONTEXT.md, CHECKLIST.md, and a .status file for new work.

32|6|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/HSUNEH/dev_sys_template --skill planwithme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planwithme
Source: https://github.com/HSUNEH/dev_sys_template/tree/main/cwm/skills/planwithme
Command: npx skills add https://github.com/HSUNEH/dev_sys_template --skill planwithme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures every new development task starts with a formal plan, creating PLAN.md, CONTEXT.md, CHECKLIST.md and a .status file to establish clear expectations, alignment, and traceability before coding begins.

Core Features & Use Cases

  • Automatically generates a four-document plan set (PLAN.md, CONTEXT.md, CHECKLIST.md) plus a .status gate that tracks the task lifecycle.
  • Applies to software development, research, and feature work requiring upfront design, approvals, and progress tracking.
  • Use case: when starting a new feature, run the planwithme skill to lock requirements, decisions, and a ready-to-implement checklist.

Quick Start

Create PLAN.md, CONTEXT.md, CHECKLIST.md and a .status file in the project's plan directory to begin the workflow.

Frequently Asked Questions about planwithme

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

FAQPage Schema
How do I generate planning documentation before starting software development?

Generate planning documentation by creating PLAN.md, CONTEXT.md, and CHECKLIST.md files to establish formal requirements, expectations, and traceability before coding begins.

What is the best way to track project requirements and approvals upfront?

Track project requirements and approvals upfront by generating a .status gate file alongside CONTEXT.md, locking decisions and establishing a clear task lifecycle before implementation.

Can I use a project checklist and plan workflow for research and feature work?

A project checklist and plan workflow applies directly to software development, research, and feature work requiring upfront design, approvals, and progress tracking to anchor new tasks.

How do I prevent relative path issues when creating project management files?

Prevent relative path issues by using absolute project-root paths based on a .cwm initialized root, ensuring all generated planning artifacts anchor correctly within the project directory.

What files do I need to align work before coding begins?

To align work before coding begins, you need PLAN.md, CONTEXT.md, CHECKLIST.md, and a .status file in the project's plan directory to formalize task expectations and traceability.

Why does upfront alignment require a .status file in software development?

Upfront alignment requires a .status file to act as a lifecycle gate, tracking the progress of the generated plan set and ensuring traceability from requirements to implementation.