What problem does it solve? Engineering and SHIP skills each need to know where work items (tickets, issues, specs) and where domain/decision documents live in a repository. Without a recorded answer, every downstream skill guesses its own convention, producing inconsistent or fictional workflows. This Skill decides both once and records them in a single block that all downstream skills read. ## Core Features & Use Cases - One-time repo configuration: Explores the repo (git remotes, existing CLAUDE.md/AGENTS.md, tickets/, CONTEXT.md, monorepo signals), presents findings with recommended defaults, confirms, then writes an ## Engineering skills block. - Solo/local default with team mode-switch: Defaults to local markdown tracking (tickets/<feature-slug>/, ISSUES.md, Status: lines) and a single-context CONTEXT.md + docs/decisions/ layout; switches up to GitHub Issues or a client tracker only when a team genuinely uses one. - Guardrails against over-scaffolding: Skips prototypes, skips triage config when no triage skill is installed, edits the existing block in place, and never creates AGENTS.md when CLAUDE.md exists. - Use Case: Before running plan-work-tickets or implement-spec on a fresh solo Next.js/TypeScript repo, run this Skill once so every downstream skill reads the same recorded tracker and doc layout instead of inventing its own. ## Quick Start Ask the AI to set up this project for the engineering skills so it records where tickets and docs live before you start shipping.
