← ClaudeAtlas

setup-pathmode-workflowlisted

Interview the user about their development workflow and capture the answers as durable context. Use when starting a new project with Pathmode, onboarding a teammate to an existing project, or when intent specs feel disconnected from how the team actually ships. Output is workflow conventions the next agent session will read.
pathmodeio/claude-plugin · ★ 1 · AI & Automation · score 67
Install: claude install-skill pathmodeio/claude-plugin
<what-to-do> Walk the user through the workflow questions below. Ask ONE question at a time. For each question, propose your best-guess answer based on what you can see in the repo (package.json scripts, CI config, README, existing PRs). The user accepts or corrects. Questions to cover (in order): 1. **Primary agent**: Which AI coding agent does the user primarily work with? (Claude Code, Cursor, Windsurf, Copilot, mixed) 2. **Issue tracker**: Where do tickets live? (Linear, Jira, GitHub Issues, none yet) 3. **Test command**: What does the user run to prove code works locally? (e.g., `npm test`, `pytest`, `pnpm vitest`) 4. **Build/typecheck command**: What does the user run to prove code compiles? (e.g., `npm run build`, `tsc --noEmit`) 5. **PR conventions**: How does code get reviewed before merge? (draft PR + review, trunk-based, solo) 6. **Status mapping**: What concrete event marks an intent as `shipped`? As `verified`? (merge to main, deploy to prod, metric hold for 1 week) 7. **Implementation note convention**: Where should agent decisions get captured? (Pathmode `log_implementation_note`, ADR file, commit messages, PR descriptions) When all questions are answered, output a single self-contained block the user can paste into their `CLAUDE.md` file (or the equivalent for their agent). Format: ```markdown ## Pathmode Workflow Conventions - Primary agent: [answer] - Issue tracker: [answer] - Test: `[command]` - Typecheck/build: `[command]` - PR conventions: [answer]