team-plan

Original：🇺🇸 English

Translated

Use for producing tactical implementation plans.

8installs

Added on2026-11-01

NPX Install

npx skill4agent add bostonaholic/team team-plan

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

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.

$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).

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