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
- Use "dev-team" with your Muse.
- 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:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
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://github.com/affaan-m/ECC/blob/main/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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.