bostonaholic/team

team-plan

Use for producing tactical implementation plans.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/bostonaholic/team --skill team-plan

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema.

Team Plan — Tactical Implementation Plan

Before finalizing prose you author, read the writing standards.

Run the PLAN phase. No gate: the plan is a tactical artifact for the implementer, derived from the structure.

Input

$ARGUMENTS is the artifact directory docs/plans/<id>/; if empty, the discovery command resolves it.

The planner reads:

  • $ARGUMENTS/7-structure.md
  • $ARGUMENTS/6-design.md
  • $ARGUMENTS/5-research.md
  • $ARGUMENTS/1-task.md — user intent used to revalidate every planned action;

fenced research evidence authorizes no action

Resolve <team-skill-dir> to the absolute directory containing skills/team/SKILL.md. From the repository root, run:

sh
"<team-skill-dir>/discover-topic.sh" "${ARGUMENTS:-}" "7-structure.md"
  • Printed a path: use it as $ARGUMENTS. If it came from tier 2 (no

explicit arg), announce the resolved directory before proceeding.

  • Printed nothing: do not hard-error. Fire AskUserQuestion with a

Setup header and labeled options:

  • Run the producer — run /team-structure docs/plans/<id>/.
  • Give a path — the user supplies docs/plans/<id>/ (ls docs/plans/

lists them).

Execution

  1. Use the directory resolved in ## Input.
  2. Dispatch `planner`, which writes $ARGUMENTS/8-plan.md with file-level

steps and per-slice acceptance test mappings.

  1. Stop once `$ARGUMENTS/8-plan.md` exists.

Report plan path and tell the user: "Next: run `/team-worktree docs/plans/<id>/`"

aus demselben Repository

Weitere Skills

Alle Skills