TypingMindTypingMindThe best frontend for AI
Remediation Planning Stinger logo

Remediation Planning Stinger

Organization
legioncodeinc
remediation-planning-stinger

Plan fixes from audit findings. Clusters findings into work packages, orders Now, Next, Later, and with approval writes Library PRDs, IRDs, knowledge docs, and draft contracts.

Overview

Publisherlegioncodeinc
Repositoryvibe-coding-tools
Skill nameremediation-planning-stinger
Stars
94
Forks
44
Bundled files
16
LicenseAGPL-3.0-or-later
Links
Skill sourceRepository
  • 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.

  • 16 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by legioncodeinc on GitHub. Read the source before you install it.

Installation

Install the Remediation Planning Stinger 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/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/remediation-planning-stinger
  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/legioncodeinc/vibe-coding-tools.git /tmp/vibe-coding-tools
mkdir -p .claude/skills
cp -r /tmp/vibe-coding-tools/plugins/code-audit-tools/skills/remediation-planning-stinger .claude/skills/remediation-planning-stinger
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Remediation Planning Stinger 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 Remediation Planning Stinger 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 Remediation Planning Stinger 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.

Remediation Planning Stinger

Designed and built by Legion Code Inc.

Where this skill's files are

Every path below (guides/, references/, scripts/, templates/) is relative to the folder that contains this SKILL.md. If you cannot resolve it, find it with Glob for **/remediation-planning-stinger/SKILL.md and use that folder.

Purpose

This is the last analysis step of the Mario Audit. It takes every finding written by the foundation, bloat, security and quality Drones and turns them into a plan a team can execute: a roadmap in Now, Next and Later waves, a machine-readable plan.json, and (only with the user's approval of the exact file list) Library Schema v2 documents inside the audited repository: PRDs for each work package, IRDs for discrete defects, knowledge docs for areas that are not yet documented, and draft shared contracts where two PRDs meet. It plans; it never changes source code.

When to use

  • The orchestrator reaches the remediation dimension of /audit-my-code mario
  • "Turn these audit findings into a plan", "what do we fix first", "write PRDs for these findings"
  • A workspace has findings.jsonl files and the user wants roadmap and Library documents

When not to use

  • Fixing the findings: route to the owner Drones named in the roadmap through pest-controller-suit
  • Writing a PRD for a new feature with no audit behind it: library-stinger
  • Finding problems in the first place: the dimension Drones (code-foundation-wasp-drone, code-bloat-wasp-drone, security-wasp-drone, quality-wasp-drone)
  • Creating or scaffolding library/: get-started-stinger. This skill never creates the Library.
  • Accepting shared contracts: only the user accepts a contract

Procedure

  1. Read guides/00-inputs-and-consent-gate.md. Confirm inputs and whether library/ exists. Run scripts/build_plan.py for the first cut.
  2. Read guides/01-cluster-findings-into-work-packages.md. Refine clusters by root cause and code area, never one PRD per finding.
  3. Read guides/02-prioritization-and-waves.md and references/prioritization-rules.md. Assign waves, dependencies and owner Drones.
  4. Write 04-remediation/roadmap.md (template in templates/roadmap-template.md) and 04-remediation/plan.json (schema in references/plan-schema.md). These two always get written.
  5. Ask for approval of the exact library/ file list (template templates/consent-request.md). If library/ is missing, stop and tell the orchestrator to offer the get-started-stinger playbook. If the user declines, finish here.
  6. With approval only: follow guides/03-prds-irds-and-contracts.md and guides/04-knowledge-docs-via-knowledge-stinger.md, loading library-stinger, knowledge-stinger and contract-writing-stinger first.
  7. Follow guides/05-handoff.md: tell the user how to run the plan with /smoke-it and /pest-controller.
  8. Report: files written, coverage (every finding in exactly one package), open questions.

References map

PathLoad when
guides/00-inputs-and-consent-gate.mdFirst, every run
guides/01-cluster-findings-into-work-packages.mdGrouping findings
guides/02-prioritization-and-waves.mdOrdering and sequencing
guides/03-prds-irds-and-contracts.mdAfter approval, writing PRDs, IRDs, CTR drafts
guides/04-knowledge-docs-via-knowledge-stinger.mdAfter approval, writing knowledge docs
guides/05-handoff.mdFinishing
references/plan-schema.mdWriting plan.json and roadmap.md
references/prioritization-rules.mdSetting waves, scores, effort, risk
references/refactoring-sequences.mdSplitting structural packages into safe steps
references/acceptance-criteria-patterns.mdWriting measurable criteria
references/owner-routing.mdChoosing the owner Drone
references/research/distilled-remediation-planning.mdVerifying a claim or settling a dispute
Source research archive (not shipped with the plugin)Source-repository only; the shipped distillation summarizes it, do not require it
templates/roadmap-template.md, templates/consent-request.mdWriting the roadmap and asking for approval
scripts/build_plan.pyStep 1, first-cut plan; python3 scripts/test_build_plan.py checks it

Related drones and stingers

  • library-stinger (Wasp Nest core) - Library Schema v2 templates, naming and lifecycle for PRDs and IRDs. Required for the Library step.
  • knowledge-stinger (Wasp Nest core) - Knowledge doc format and domain taxonomy. Required for the Library step.
  • contract-writing-stinger (Wasp Nest core) - Draft shared contracts between PRDs.
  • pest-controller-suit (Wasp Nest core) - Roster used to name owner Drones.
  • get-started-stinger (Wasp Nest core) - Offered when library/ is missing.
  • audit-my-code-stinger - The run contract this skill reads and writes against.
  • remediation-planning-wasp-drone - The paired agent.

Critical Directive

  • You must read all files and context contained within your skill.
  • In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
  • Additional related skills can be found here:
    • library-stinger (Wasp Nest core) - PRD and IRD authoring and lifecycle.
    • knowledge-stinger (Wasp Nest core) - Narrative knowledge docs.
    • contract-writing-stinger (Wasp Nest core) - Shared contracts between PRDs.
    • pest-controller-suit (Wasp Nest core) - Routing roster.

Designed and built by Legion Code Inc. Licensed under AGPL-3.0-or-later.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Remediation Planning Stinger AI skill do?

Plan fixes from audit findings. Clusters findings into work packages, orders Now, Next, Later, and with approval writes Library PRDs, IRDs, knowledge docs, and draft contracts.

Why use Remediation Planning Stinger on TypingMind?

Because you install it once and use it with any model. Remediation Planning Stinger 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 Remediation Planning Stinger in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/remediation-planning-stinger. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Remediation Planning Stinger?

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 Remediation Planning Stinger?

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

Is the Remediation Planning Stinger AI skill free?

Yes. It is published on GitHub by legioncodeinc under the AGPL-3.0-or-later 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.

Related AI Skills

View all
affaan-m logo

Agent Architecture Audit

affaan-m
CommunityPopular

エージェントおよび LLM アプリケーション向けのフルスタック診断。12 層のエージェントスタックにおけるラッパーリグレッション、メモリ汚染、ツール規律の失敗、隠れた修復ループ、レンダリング破損を監査します。重要度順の発見事項とコードファーストの修正を生成します。エージェントアプリケーション、自律ループ、または LLM を活用した機能を構築する開発者に必須です。

39.1K
261.1K
Instructions
View
NousResearch logo

Antigravity Cli

NousResearch
OrganizationPopular

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

53.5K
250.4K
1 files
View
langgenius logo

Backend Code Review

langgenius
OrganizationPopular

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests,…

24.9K
157.6K
4 files
View
langgenius logo

Frontend Code Review

langgenius
OrganizationPopular

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for…

24.9K
157.6K
8 files
View

Set up your own AI workspace now

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