support-agent

Answers codebase and agent-pipeline questions while maintaining CenCon documentation read-only.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill support-agent-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: support-agent
Source: https://github.com/thefrederiksen/devthrottle/tree/main/.claude/skills/support-agent
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill support-agent-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and stakeholders often need quick answers about how a codebase works or what the other agents in a multi-agent development pipeline are doing, without interrupting the agents that write code or manage issues. This Skill provides a dedicated read-only question-answering seat that explains the cc-director codebase, reports pipeline status from GitHub issue labels, and keeps the CenCon architecture documents accurate. ## Core Features & Use Cases - Codebase Q&A: Searches code, docs, and git history with Grep/Glob/Read and answers with file:line citations, never from memory. - Pipeline status reporting: Reads flow:* labels on GitHub Issues via gh to summarize what the Product, Developer, and QA agents are doing and what is stuck. - CenCon doc maintenance: The only write access it has — updates docs/cencon/ (architecture_manifest.yaml, security_profile.yaml, INDEX.md) and regenerates diagrams when the architecture drifts. - Use Case: Ask "what are the agents doing right now" and get a stage-by-stage summary of open issues, including escalations marked flow:needs-human and repeatedly rejected items. ## Quick Start Ask the support agent to explain how a specific part of the cc-director codebase works or to summarize the current state of the issue pipeline.

Frequently Asked Questions about support-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check what my coding agents are working on?▼

Ask the support agent for a pipeline summary. It runs read-only gh issue list queries filtered by flow:* labels and maps each label to a stage and owning agent, then summarizes what is queued, stuck, or finished.

How do I get answers about a codebase without changing code?▼

Use a read-only support agent that searches with Grep, Glob, and Read before answering. It cites file:line references and prefers architecture docs as a map, so it explains code without ever editing it.

Can the support agent create or move GitHub issues?▼

No. The support agent is strictly read-only with respect to issues and product code. It never creates, edits, labels, or closes issues; when it finds work that should be done, it routes the request to the Product Agent.

What files is the support agent allowed to write?▼

Only the CenCon documents under docs/cencon/, including architecture_manifest.yaml, security_profile.yaml, INDEX.md, and DEVELOPMENT_METHOD.md. It uses the cencon-generate skill and cc_docgen to refresh docs and diagrams.

What happens when architecture docs drift from the code?▼

The agent answers from the actual code, notes that the CenCon docs have drifted, and offers to refresh them. A 30-day drift rule applies, enforced by the /review-code process.