natural-workflow

Guide users through CCPM's six-command workflow from plan to done.

9|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/duongdev/ccpm --skill natural-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: natural-workflow
Source: https://github.com/duongdev/ccpm/tree/main/skills/natural-workflow
Command: npx skills add https://github.com/duongdev/ccpm --skill natural-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through CCPM's streamlined 6-command lifecycle from plan to done, reducing context switching and cognitive load.

Core Features & Use Cases

  • Six-command lifecycle: plan, work, sync, commit, verify, done, guiding you end-to-end.
  • Auto-activation: Suggests actions when you ask about starting tasks, committing changes, or finishing work.
  • Seamless PR flow: Creates plan, commits, and PR-ready state automatically.

Quick Start

Start a new task with /ccpm:plan "Add feature" and then follow with /ccpm:work PSN-123, /ccpm:sync, /ccpm:commit, /ccpm:verify, /ccpm:done PSN-123.

Frequently Asked Questions about natural-workflow

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

FAQPage Schema
How do I automate my workflow from task planning through pull request creation?

Workflow automation guides you through a six-command lifecycle—plan, work, sync, commit, verify, done—that handles task planning, implementation tracking, and PR creation automatically across Jira, Confluence, Linear, and your codebase, eliminating manual context switching.

Can I use this workflow with Jira, Linear, and Confluence together?

Yes, the six-step workflow integrates with Jira, Confluence, Linear, and your codebase simultaneously, auto-detecting project context and syncing task state across all platforms without manual updates.

How do I start and track a task through completion?

Start with /ccpm:plan to define the task, then /ccpm:work to begin, /ccpm:sync to save progress, /ccpm:commit for changes, /ccpm:verify to check readiness, and /ccpm:done to finalize—each step auto-generates checklists, estimates complexity, and persists state.

What happens when I commit changes—does it create a pull request automatically?

The commit step prepares PR-ready state by identifying file changes and generating implementation metadata; the workflow then flows into verification and completion steps that support seamless PR creation.

Do I need to manually plan implementation tasks or does this generate checklists?

The workflow auto-generates implementation checklists, detects file changes, estimates task complexity, and persists progress in Linear—no manual planning required beyond the initial task description.