<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

planning-setup

This skill is part of Misbah Khursheed's Build Like This workflow. Thinking, evidence, and explicit trade-offs come before generated output.

Project identity and sources of truth

The repository where this skill is installed is the host project being built. Build Like This is the method used to build it; mstack only installs and reconciles method resources. Do not assume mstack or Build Like This is the product unless project-owned sources explicitly identify this repository as mstack itself.

Use project-owned docs/, decisions, executable code, and tests as sources of truth. .mstack/templates/ are reference scaffolds to copy and adapt into project-owned documents, not product requirements and not a replacement for docs/.

Purpose

Make tracer-bullet tickets and session continuity write to one agreed tracker and doc layout so agents do not invent parallel systems.

Required inputs

• Repository remotes, existing AGENTS.md/CLAUDE.md, docs/ layout, and any prior docs/agents/ issue-tracker notes.
• Available CLIs (gh, glab) and whether local markdown tickets are preferred.

If a missing input would materially change the result, state the gap and obtain or discover it before proceeding. Otherwise label the assumption and continue.

Process

1. Inspect remotes, docs/, and agent instruction files without changing them yet.
2. Ask one question at a time: issue tracker (GitHub, GitLab, local markdown under a chosen path, or other with a freeform adapter note), then triage labels if applicable, then glossary/ADR paths if non-default.
3. Recommend defaults from evidence (GitHub remote → GitHub; otherwise local markdown).
4. Write docs/agents/issue-tracker.md with tracker choice, commands or paths, label map if any, and glossary/ADR locations.
5. Add a short pointer block in the existing AGENTS.md or CLAUDE.md rather than creating a second instruction root.
6. Stop after setup; do not create tickets or specs in this skill.

Output contract

• docs/agents/issue-tracker.md describing tracker, paths, and labels.
• A minimal pointer in existing agent instructions to that file.
• Confirmed defaults for ticket-graph and implement-task-graph.

Guardrails

• Do not install duplicate skill trees or second copies of mstack resources.
• Do not invent a tracker the repository cannot reach; fall back to local markdown when CLIs or remotes are missing.
• Do not rewrite AGENTS.md beyond a small pointer section.

Delegation and parallel safety

• Material lifecycle work must delegate at least one bounded specialist lane when subagents are available. Prefer two or more concurrent lanes only for independent evidence gathering, analysis, or non-overlapping file ownership.
• The active lead owns integration and acceptance. Supporting agents do not recursively delegate unless explicitly promoted to lead a named lane.
• Assign distinct outputs and ownership. Serialize shared docs, contracts, schemas, migrations, deployments, external writes, and overlapping file edits.
• When subagents are unavailable, perform the same named specialist passes sequentially and state that constraint instead of implying parallel verification.
• Delegation never grants permission for outreach, consequential external actions, destructive changes, paid resources, or production operations.

End with the evidence gathered, verification performed, and any residual risk or unresolved decision.