ayoubben18/ab-method / .agents/skills/ab-mastermind
ab-mastermind
VerifiedThe intelligent entry point to the AB Method. Use when the user isn't sure which workflow they need, asks whether to create a goal or a task, or wants to understand how the AB Method works end to end. Routes intent to the right workflow instead of reimplementing it.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.7 KB |
SKILL.md
View on GitHub---
name: ab-mastermind
description: The intelligent entry point to the AB Method. Use when the user isn't sure which workflow they need, asks whether to create a goal or a task, or wants to understand how the AB Method works end to end. Routes intent to the right workflow instead of reimplementing it.
---
This skill runs the AB Method **mastermind** workflow.
Follow the workflow defined in `.ab-method/core/mastermind.md` exactly — it contains the full routing logic, the goal-vs-task decision guide, and the end-to-end explanation.
Before doing anything, check `.ab-method/structure/index.yaml`. It defines where every workflow reads from and writes to. Paths are user-configurable; never hardcode them.
**Locating `.ab-method/`.** Every `.ab-method/...` path — here and inside the workflow files — is resolved in this order:
1. **The project root (the current working directory) first.** If `<project>/.ab-method/...` exists, use it. A project's own `.ab-method/structure/index.yaml` is how it customises its paths, so it always wins — check for it even when the bundled copy is right there.
2. **Only if the project has no such file** (AB Method installed as a plugin rather than with `npx ab-method`), read the bundled copy: `../../../.ab-method/` relative to this `SKILL.md`.
The bundled copy is read-only reference material. Every path the index or a workflow names (`docs/...`, `CONTEXT.md`, `UBIQUITOUS_LANGUAGE.md`, ...) is relative to the **project root** — never to the folder the bundled files live in. Never write inside that folder.
Mastermind is deliberately thin: it discovers the available `ab-*` workflow skills at runtime, matches the user's intent, and delegates to the matching skill. It never reproduces another workflow's process.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |