Code Plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
Install
npx skills add initializ/forge --skill code-plangit clone --depth 1 https://github.com/initializ/forge.git /tmp/forge
mkdir -p ~/.claude/skills
cp -r /tmp/forge/forge-skills/local/embedded/code-plan ~/.claude/skills/code-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Plan Skill Generate a structured plan for implementing a task in a specific repository. The plan is the bridge between "I have a ticket" and "let me start writing code" — it lists files to create, files to modify, tests to add, and risks before any code is written. This skill produces JSON. It does **not** write code; that is `code_agent_*`'s job. ## When to use this skill - The user provides a Linear ticket, GitHub issue, or free-form task description and asks you to implement it. - **Before** any `code_agent_write`, `code_agent_edit`, or `github_commit` tool call. - When the user explicitly asks for a plan. ## When NOT to use this skill - Tiny single-file edits (1–3 lines). Just edit directly. - Pure exploration tasks. Use `grep_search` / `directory_tree` instead. - Pure scaffolding tasks (e.g. "create a new React app"). Use `code_agent_scaffold` instead. ## Plan-then-execute discipline Once a plan is generated, present its `summary` and `files_to_modify` / `files_to_create` lists to the user before writing code. Do NOT proceed to implementation if the plan returns `complexity: "high"` or non-empty `risks` without acknowledging them to the user. The plan is a contract: subsequent code-writing tool calls should match files listed in the plan. If the plan turns out to be wrong, regenerate it rather than silently drifting from it. ## Workflow integration Canonical sequence for a ticket-to-PR flow:
Details
- Skill name
code-plan- Repository
- initializ/forge
- Path
forge-skills/local/embedded/code-plan/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Code Plan skill do?
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
How do I install the Code Plan skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add initializ/forge --skill code-plan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Code Plan popular?
It lives in initializ/forge, which has 230 GitHub stars and 17 forks.
Related skills
Code Agent
230initializ/forge
General-purpose coding agent that reads, writes, and edits code, and searches codebases.
Code Review
230initializ/forge
AI-powered code review for diffs and individual files using LLM analysis
Code Review Github
230initializ/forge
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge
Code Review Standards
230initializ/forge
Discover and apply organization coding standards from .forge-review/ configuration
Codegen HTML
230initializ/forge
Scaffold and iterate on standalone Preact + HTM applications with zero build dependencies
Waf Assessment
206thomast1906/github-copilot-agent-skills
Assess Azure architectures against Well-Architected Framework (WAF) five pillars - Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency. Provide scores and recommendations.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.