使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/bostonaholic/team --skill team-plan開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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:
"<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
AskUserQuestionwith 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
- Use the directory resolved in
## Input. - Dispatch `planner`, which writes
$ARGUMENTS/8-plan.mdwith file-level
steps and per-slice acceptance test mappings.
- Stop once `$ARGUMENTS/8-plan.md` exists.
Report plan path and tell the user: "Next: run `/team-worktree docs/plans/<id>/`"