Technical Plan Guard logo

Technical Plan Guard

Community
xigua-wang
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.

Overview

Publisherxigua-wang
Repositoryskill-doctor
Skill nametechnical-plan-guard
Stars
273
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by xigua-wang on GitHub. Read the source before you install it.

Installation

Install the Technical Plan Guard AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/xigua-wang/skill-doctor/tree/main/.codex/skills/technical-plan-guard
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git 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-guard
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Technical Plan Guard in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Technical Plan Guard on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Technical Plan Guard is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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
  • risks and tradeoffs
  • validation steps

If the repository already contains a broader strategy document such as docs/technical-plan.md, treat it as context, not as the per-request plan file.

Frequently asked questions

What does the Technical Plan Guard AI 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.

Why use Technical Plan Guard on TypingMind?

Because you install it once and use it with any model. Technical Plan Guard is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Technical Plan Guard in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/xigua-wang/skill-doctor/tree/main/.codex/skills/technical-plan-guard. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Technical Plan Guard?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Technical Plan Guard?

As many as you like. As long as a model supports skills, you can use Technical Plan Guard with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Technical Plan Guard AI skill free?

Yes. It is published on GitHub by xigua-wang under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇