This skill should be used when the user runs "/devsquad:setup", asks to "configure devsquad", "set up delegation", "change enforcement mode", or "update agent preferences". Guides through environment detection, preference capture, and config generation.
This skill should be used when the user asks to "run a workflow", "chain skills together", "execute a feature workflow", or wants to automate a multi-step process (create feature branch -> generate code -> test -> clean up).
Work the Loopback feedback queue — the cross-project bus where real product usage lands as actionable items (pinned UI feedback, backend failures with captured response bodies, UX papercuts, AI-feature feedback with run metadata) and where fixes are written back so pins turn green. Use this whenever the user says…
AGENTS.md instructions for joshidikshant/loopback, covering agent instructions, working the loopback queue, the loop, attachments — reference vs asset and filing feedback (agents report too).
Claude Code instructions for joshidikshant/loopback, a project described as: Interactive feedback layer between the app you're building and your coding agents (MCP). Pins carry the failing request; Claude Code, Codex, and Gemini CLI work one queue; a verified fix turns the pin green.
Gemini CLI instructions for joshidikshant/loopback, a project described as: Interactive feedback layer between the app you're building and your coding agents (MCP). Pins carry the failing request; Claude Code, Codex, and Gemini CLI work one queue; a verified fix turns the pin green.
Loopback feedback hub for Claude Code: the loopback skill (work the feedback queue) + MCP registration for the project-tagged feedback bus. Codex gets the same via .agents/skills + config.toml; Gemini via AGENTS.md + settings.json.