Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

ct-writing-plans

Use when writing implementation plans after a design or spec has been approved.

Exécuter dans Manus

Aperçu

Use when writing implementation plans after a design or spec has been approved.

Commande d'installation

npx skills add https://github.com/dnldxn/claptrap --skill ct-writing-plans

Copiez et collez cette commande dans Claude Code pour installer le skill

Source

dnldxn/claptrap

Étoiles0

Forks0

Mis à jour20 mai 2026 à 15:55

SKILL.md

readonly

name	ct-writing-plans
description	Use when writing implementation plans after a design or spec has been approved.

OPERATION OVERRIDE: The instructions in this file take precedence over conflicting instructions in any other Skills.

REQUIRED SUB-SKILL: Use writing-plans with the following modifications:

Plan files MUST be saved to .planning/plans/YYYY-MM-DD-<order>-<spec-slug>-<plan-slug>.md
Use two-digit <order> values (01, 02, ...).
Identify the parent spec/design file before writing plans (normally under .planning/specs/).
Derive <spec-slug> from the parent spec's title/header line (usually H1) as a short kebab-case visual hint.
The parent spec/design linkage MUST be captured in .planning/state.html when each plan is written.

After saving each plan file, invoke ct-manage-state-file to record the current state and include:

which plan file was written
the parent spec/design file for that plan

When parent linkage is uncertain, make a best-effort guess and explicitly label it as inferred so ct-manage-state-file can mark the mapping as inferred in .planning/state.html.

Spec: $ARGUMENTS

Plus depuis ce dépôt

même dépôt

ct-grill-me

dnldxn/claptrap

Use when starting a new design or spec to interview the user, answer open questions, and draft a specification.

2026-06-030

gh-grill-me

dnldxn/claptrap

Use when starting a new design/spec that should be saved as a GitHub Issue on the Project board after user approval.

2026-05-270

gh-implement

dnldxn/claptrap

Use when executing an implementation plan from a GitHub Project board, committing directly to main with Closes trailers.

2026-05-270

gh-writing-plans

dnldxn/claptrap

Use when breaking a GitHub spec issue into implementation plan sub-issues on the Project board, optionally updating the spec issue body with meaningful new constraints or decisions.

2026-05-270

ct-manage-state-file

dnldxn/claptrap

Use when a Claptrap workflow needs to update or resync `.planning/state.html` after spec, plan, implementation, review, merge, or archive changes.

2026-05-210

ct-implement

dnldxn/claptrap

Use when you have a written plan and are ready to execute it in the current workspace.

2026-05-200

Source

dnldxn

dnldxn/claptrap

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Commande d'installation

Téléchargement

Exécuter dans Manus

Utile pourSOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières13-1082L4

name	ct-writing-plans
description	Use when writing implementation plans after a design or spec has been approved.

OPERATION OVERRIDE: The instructions in this file take precedence over conflicting instructions in any other Skills.

REQUIRED SUB-SKILL: Use writing-plans with the following modifications:

Plan files MUST be saved to .planning/plans/YYYY-MM-DD-<order>-<spec-slug>-<plan-slug>.md
Use two-digit <order> values (01, 02, ...).
Identify the parent spec/design file before writing plans (normally under .planning/specs/).
Derive <spec-slug> from the parent spec's title/header line (usually H1) as a short kebab-case visual hint.
The parent spec/design linkage MUST be captured in .planning/state.html when each plan is written.

After saving each plan file, invoke ct-manage-state-file to record the current state and include:

which plan file was written
the parent spec/design file for that plan

When parent linkage is uncertain, make a best-effort guess and explicitly label it as inferred so ct-manage-state-file can mark the mapping as inferred in .planning/state.html.

Spec: $ARGUMENTS