team-structurelisted

# Team Structure — How Do We Get There? Run the STRUCTURE phase. It runs autonomously and advances to PLAN — there is **no gate** here. Nothing is presented for approval mid-run. ## Input `$ARGUMENTS` is the artifact directory: `docs/plans/<id>/`. If empty, the discovery block below resolves it. The `structure-planner` reads: - `$ARGUMENTS/design.md` (the reviewed design — the latest `$ARGUMENTS/design-review-<n>.md` must carry a passing verdict) - `$ARGUMENTS/research.md` - `$ARGUMENTS/task.md` (for cross-reference, not for re-litigating intent) Resolve the artifact directory by running this self-contained block (one bash call — agent threads reset cwd between calls). The predecessor filter requires a `design.md` whose latest `design-review-<n>.md` carries a passing verdict (APPROVE or COMMENT), so unreviewed or REQUEST-CHANGES candidates are skipped: ```sh # Three-tier artifact-directory discovery (archetype A). # ID_RE + PHASE_FILES canonical from hooks/session-start-recover.mjs. # PHASE_FILES recency mirrors findActiveTopic() in session-start-recover.mjs. # NOTE: this block is duplicated across 8 skills by design (see docs/architecture.md); future: shared discover-topic.sh. ID_RE='^([A-Za-z][A-Za-z0-9_]*-[0-9]+|[0-9]{4}-[0-9]{2}-[0-9]{2})-[a-z0-9][a-z0-9-]*$' PHASE_FILES="task questions research design structure plan" PRED="design.md" # predecessor artifact this skill consumes # Tier 1 — explicit: $ARGUMENTS names an existing dir → use verbatim. if [ -