Dev Team
One topic, four lenses: PM, Architect, Developer, and QA respond together, then a synthesis names the tensions.
- What
- One topic, four lenses: PM, Architect, Developer, and QA respond together, then a synthesis names the tensions.
- Cost
- Free
- Needs
- the Muse app (mobile or web). No installation, no API key, no extra account.
- Level
- Beginner — the Muse app (mobile or web).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a multi-persona session skill that runs your topic past four fixed roles in one go: the PM (user value, scope, prioritization, definition of done), the Architect (system design, scalability, technical risk, integration points), the Developer (implementation complexity, effort, edge cases, technical debt), and the QA engineer (testability, acceptance criteria, failure modes, regression risk). Each persona gives a first reaction, three key concerns, a first action, and one question for the team, all under 250 words and strictly analysis-only: no file edits, no commands, no state changes. Then comes the synthesis, which is the real product: it names what all four roles agree on and calls out tensions explicitly instead of averaging them into a diplomatic middle (if PM and QA conflict on scope, the conflict gets named, not split). It knows what it is not: not code review (personas don't read diffs), not an adversarial verdict (that's the council skill), not a pick-your-own team (that's team-builder). By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: written for Claude Code's parallel subagents; in Muse you get the same four perspectives plus synthesis in a single response instead of true parallel agents, which is fine for shaping a proposal. If your topic emerged from a long thread, distill it to one paragraph first; pasting the whole transcript dilutes every persona. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Dev Team is a free Muse skill that runs your topic past four fixed roles in one go, with a PM, Architect, Developer, and QA responding together, then a synthesis naming the tensions. Each persona gives a first reaction, three concerns, a first action, and one question, strictly analysis-only with no edits or commands.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "dev-team" with your Muse. Prerequisites: the Muse app (mobile or web). No installation, no API key, no extra account. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/dev-team/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Dev-team this topic: [your feature, proposal, or question in one paragraph: what is proposed, what constraints matter, what you want back]." 3. Read the four perspectives, then the synthesis. If a tension needs a verdict rather than shaping, ask Muse to run the topic as an adversarial decision next. Tip: distill long threads to the one-paragraph problem statement before pasting. Focused input gives focused personas; a pasted transcript gives mush. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets or API keys into it, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.