Technical Plan Guard
Use this skill when the user introduces a new requirement, feature request, scope change, or implementation direction for this repository. Before coding, create a technical plan in docs using the required naming convention docs/tech-plan-<topic>-<YYYYMMDD>-session-<session-id>.md, then align the implementation to that plan.
Install
npx skills add xigua-wang/skill-doctor --skill technical-plan-guardgit clone --depth 1 https://github.com/xigua-wang/skill-doctor.git /tmp/skill-doctor
mkdir -p ~/.claude/skills
cp -r /tmp/skill-doctor/.codex/skills/technical-plan-guard ~/.claude/skills/technical-plan-guardPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Technical Plan Guard For this repository, any new requirement should start with a technical plan document under `docs/` before implementation work begins. ## When to use Use this skill when the user: - asks to add a new feature or workflow - changes product or technical direction - requests a non-trivial refactor - asks for a new skill, rule, or repository convention Skip this skill only for: - typo or wording fixes - trivial one-line bug fixes - purely exploratory questions with no requested change ## Required output Create a technical plan file in `docs/` with this filename pattern: `docs/tech-plan-<topic>-<YYYYMMDD>-session-<session-id>.md` Rules: - use lowercase kebab-case for `<topic>` - keep `<topic>` short and specific, usually 2 to 6 words - use the current local date in `YYYYMMDD` - keep the literal segment `session` - use a short session identifier in `<session-id>`, such as `001`, `alpha`, or `new-skill` Example: `docs/tech-plan-new-skill-doc-rule-20260417-session-001.md` ## Working procedure 1. Infer a concise topic from the request. 2. Pick a session id that distinguishes the planning round. 3. Create the new plan file from `docs/technical-plan-template.md` if available. 4. Fill in scope, constraints, implementation steps, risks, and validation. 5. Only then proceed with code or content changes needed by the request. ## Plan content The plan should cover: - background - goal and non-goals - proposed approach - file or module impact
Details
- Skill name
technical-plan-guard- Repository
- xigua-wang/skill-doctor
- Path
.codex/skills/technical-plan-guard/SKILL.md- License
- MIT
- Repo updated
- 22 April 2026
FAQ
What does the Technical Plan Guard skill do?
Use this skill when the user introduces a new requirement, feature request, scope change, or implementation direction for this repository. Before coding, create a technical plan in docs using the required naming convention docs/tech-plan-<topic>-<YYYYMMDD>-session-<session-id>.md, then align the implementation to that plan.
How do I install the Technical Plan Guard skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add xigua-wang/skill-doctor --skill technical-plan-guard. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Technical Plan Guard popular?
It lives in xigua-wang/skill-doctor, which has 272 GitHub stars and 2 forks.
Related skills
API Triage
272xigua-wang/skill-doctor
Investigates API integration failures and remote behavior.
Deploy Router
272xigua-wang/skill-doctor
Routes deploy requests and environment-specific handoffs.
Doc Gateway
272xigua-wang/skill-doctor
Indexes project docs and links contributors to the right workflow notes.
Content to Skill
107gnipbao/content-to-skill
Converts arbitrary source material into an executable structured Codex skill package. Use when the user provides text, notes, documents, PDFs, transcripts, videos, courses, articles, repositories, workflows, chat logs, or rough ideas and asks to turn them into a Skill, SKILL.md, skill scaffold, reusable agent workflow, operational prompt, or structured capability. Also use for 把内容变成skill, 文档转skill, 视频转skill, 课程转skill, 工作流沉淀成skill, or 从资料生成可执行Skill.
Web Browse
230initializ/forge
Drive a headless browser to navigate pages, read content, click, and fill forms — for sites that need JavaScript rendering or interaction beyond a plain HTTP fetch.
Worldbook Design and Writing
224LiarMTTT/TavernWeave
Plan, split, merge, review, and write SillyTavern worldbooks independently of whole-card creation. Jointly design scene information needs, native or template loading, entry bodies, conditions, exceptions, knowledge boundaries, and paired configuration. Use for standalone worldbook work, semantic-preserving entry rewrites, and native/template/partial-mix choices. Keep character design, exact APIs, state writers, real-runtime validation, and packaging with their existing owners.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.