Skip to content

github/awesome-copilot / skills/setup-my-iq

setup-my-iq

Unverified

Create, set up, or update the personal context portfolio: structured markdown files describing who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview workflow for first-time setup and targeted edits for updates. Trigger this skill when the user asks to: set up their context, create or update their context portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder, update ADO config, change team info, update pillars, or set up any plugin configuration. Trigger when another skill fails to find context (missing files or TODO markers) and needs context populated. Also trigger when the user mentions a context change in passing (e.g., "my manager changed", "we added someone to the team") to offer a context file update. Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?". Those are answered directly from the context files referenced in the loaded custom instructions; no skill is needed.

assets/templates/tools-systems-and-config.md

View on GitHub
# Tools, Systems, and Configuration

## Primary Tools

- **IDE:** <!-- e.g., VS Code -->
- **AI:** <!-- e.g., GitHub Copilot -->
- **Project management:** <!-- e.g., Azure DevOps, Jira -->
- **Communication:** <!-- e.g., Teams, Slack -->
- **Notes:** <!-- e.g., Obsidian, OneNote -->
- **Source control:** <!-- e.g., Git -->

## <!-- Notes/Vault System -->

| Setting | Value |
|---------|-------|
| Vault/notes path | <!-- full path --> |
| Action items | <!-- path to action items file --> |

### Meeting Notes

| Setting | Value |
|---------|-------|
| Meetings folder | <!-- full path --> |
| Format | <!-- e.g., Obsidian-compatible markdown --> |
| File organization | <!-- e.g., {folder}/YYYY-MM/YYYY-MM-DD-Title.md --> |

### Meeting Tags

Tags are applied to meeting notes based on title pattern matching. Meeting type tags identify the format. Team tags identify which project/team a meeting belongs to.

| Tag | Type | Patterns |
|-----|------|----------|
| <!-- tag name --> | Meeting type | <!-- comma-separated patterns --> |
| <!-- tag name --> | Team | <!-- comma-separated patterns --> |

---

## <!-- Team/Workstream Name 1 -->

### Azure DevOps

<!-- If this workstream does not use ADO, delete this section or leave it empty. -->

| Setting | Value |
|---------|-------|
| Organization | <!-- org name --> |
| Project | <!-- project name --> |
| Team | <!-- team name --> |
| Area Path | <!-- area path --> |

### Scorecard Exclusions

| Setting | Value |
|---------|-------|
| Exclude title patterns | <!-- patterns to exclude from reports --> |

### Reporting

| Setting | Value |
|---------|-------|
| Sprint update output | <!-- path --> |
| Weekly update output | <!-- path --> |
| Weekly update prefix | <!-- e.g., weekly-update --> |
| Roadmap file | <!-- path, or leave empty to skip --> |
| Context file patterns | `*.md` |

### Strategic Pillars

<!-- These are used as grouping headers in weekly updates and sprint reports.
     Define them even if the workstream does not use ADO. The ADO Epics column
     is optional; leave it empty for non-ADO workstreams. -->

| Pillar | ADO Epics | Definition |
|--------|-----------|------------|
| <!-- pillar name --> | <!-- epic names, or empty --> | <!-- brief definition --> |

---

## <!-- Team/Workstream Name 2 -->

### Azure DevOps

<!-- If this workstream does not use ADO, delete this section or leave it empty. -->

| Setting | Value |
|---------|-------|
| Organization | <!-- org name --> |
| Project | <!-- TODO --> |
| Team | <!-- TODO --> |
| Area Path | <!-- TODO --> |

### Reporting

| Setting | Value |
|---------|-------|
| Weekly update output | <!-- path --> |
| Weekly update prefix | <!-- e.g., weekly-update --> |

### Strategic Pillars

| Pillar | ADO Epics | Definition |
|--------|-----------|------------|
| <!-- pillar name --> | | <!-- brief definition --> |

---

<!-- Add workstream sections as needed. Common settings go at the top, workstream-specific config goes under each heading.
     Every workstream needs at least: Reporting and Strategic Pillars.
     Azure DevOps is optional. -->
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall