OpenParable
Skip to content
← Back to skills

Cfn Task Planning

Productivity
cfn-task-planning

Cfn Task Planning is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Classify tasks, initialize structured configs with scope boundaries, decompose complex tasks

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/cfn-task-planning/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cfn-task-planning, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

What it does

Three-phase planning: (1) classify by type/complexity → agent specializations, (2) initialize config with scope boundaries, deliverables, acceptance criteria, (3) decompose large tasks into subtasks within tool budgets.

When to use (4 triggers)

  1. Starting CFN Loop Task Mode → Generate scope config before spawning
  2. Analyzing complexity → Select right agents and iteration thresholds
  3. Breaking down epics → Sequential subtasks when one agent can't complete
  4. Scope contracts → Establish in/out-of-scope before implementation

When NOT to use (4 anti-patterns)

  1. Well-defined and scoped → Go straight to spawning
  2. Real-time classification during execution → Planning phase only
  3. CLI mode with Redis → CLI stores in Redis, this is for Task Mode configs
  4. Simple single-step → Skip for trivial changes

How to use

Step 1 Classify: ./classify-task.sh "Create REST API..." --format=json Step 2 Init: ./init-config.sh --task-id cfn-phase-123 --task-description "..." --mode standard Step 3 Decompose: ./decompose-task.sh --task-id ... --description "..." --complexity high

Parameters

  • classify: TASK_DESCRIPTION, --format (json/simple)
  • init: --task-id, --task-description, --mode (mvp/standard/enterprise)
  • decompose: --task-id, --description, --tool-budget, --complexity

Expected output

  • Classify: {task_type, complexity, keywords_matched, suggested_agents}
  • Init: .cfn/task-configs/task-{id}.json with scope, agents, thresholds, acceptance criteria
  • Decompose: JSON array of subtasks with deliverables, tool_budget, estimated_effort

Real-world example

"Add JWT auth" → classify backend → init config with deliverables [src/auth/jwt.ts, tests/] + acceptance criteria → spawn agents with known scope