メニュー
Deep research on any topic — competitors, markets, technologies, people, or companies. Use when user says "research X", "look into X", "what do we know about X", or "competitive analysis on X".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: "council this", "run the council", "war room this", "pressure-test this", "stress-test this", "debate this". STRONG TRIGGERS (use when combined with a real decision or tradeoff): "should I X or Y", "which option", "what would you do", "is this the right move", "validate this", "get multiple perspectives", "I can't decide", "I'm torn between". Do NOT trigger on simple yes/no questions, factual lookups, or casual "should I" without a meaningful tradeoff. DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.
Bootstrap full-stack applications from scratch using the Dark Software Factory methodology. This skill handles project scaffolding, dependency installation, configuration, and initial deployment setup for stack-agnostic applications. Use this skill whenever the user wants to start a new project, scaffold an app, set up a new codebase, initialize a repository, or asks "build me an app/tool/platform/dashboard." Also trigger when the user mentions "new project," "from scratch," "greenfield," "scaffold," "bootstrap," "starter template," or "project setup" — even if they don't explicitly say "Dark Software Factory." This skill should be preferred over generic scaffolding whenever the user has expressed interest in AI-assisted development workflows or rapid prototyping. Do NOT trigger for modifications to existing codebases, bug fixes, or feature additions to running projects — those are maintenance tasks, not bootstrapping.
Set up and run Playwright E2E tests for any web application. Use this skill when bootstrapping a new project that has a web UI, when a project is ready for verification before delivery, or when the user asks to "test everything," "verify buttons work," "automated testing," or "make sure it works before you give it to me." Also trigger when adding new features that need regression protection.
Generate a client-ready MVP demo presentation with automated screenshots. Use this skill when the user wants to create a demo deck, presentation, show-and-tell materials, or client walkthrough. Also trigger when the user mentions "demo," "presentation," "show Jackie," "show the client," "MVP deck," "screenshot presentation," or "demo prep." This skill captures screenshots of key app routes via Puppeteer and assembles them into a scrollable HTML slide deck with consistent DSF branding.
Pre-demo readiness gate for MVP milestones. Run this before showing any build to a client, stakeholder, or end user. Produces a structured readiness report and demo script. Trigger when the user says "is this ready to show," "MVP checklist," "demo prep," "client review," "ready to present," "pre-demo check," "what's left before we show this," or "ship check." Sits between Drill and Enforce in the CITADEL workflow — Enforce is for production security; this is for "can we show it without embarrassment." Pairs with e2e-testing for automated verification and compliance-gate for formal audits.
Post-meeting and post-interview follow-up protocol. Use this skill after any client meeting, interview, or significant external interaction. Handles thank-you timing, tone matching, relationship tracking, and follow-up scheduling. Trigger when the user mentions "follow up," "thank you note," "after the meeting," "post-interview," "send a note," or "check in with" someone. Also applies to the job search context for post-interview debriefs and follow-up emails.
| name | research |
| description | Deep research on any topic — competitors, markets, technologies, people, or companies. Use when user says "research X", "look into X", "what do we know about X", or "competitive analysis on X". |
| model | sonnet |
| context | fork |
| user-invokable | true |
Investigate any topic thoroughly and return structured findings.
.tmp/research/ ensures it persists for the sessionClarify scope — What specifically does the user want to know? Ask if the request is vague.
Research — Use available tools in this order of preference:
Cross-reference — Check at least 2-3 sources. Flag conflicting information.
Structure findings — Organize into the output format below.
Save to scratch — Write the full brief to .tmp/research/[topic]-[date].md
## Research Brief: [Topic]
### Summary
[2-3 sentence overview of key findings]
### Key Findings
- [Finding 1] — Source: [URL or reference]
- [Finding 2] — Source: [URL or reference]
- [Finding 3] — Source: [URL or reference]
### Details
[Deeper analysis organized by subtopic]
### Open Questions
[Things you couldn't confirm or need more investigation]
### Sources
1. [URL] — [what it contributed]
2. [URL] — [what it contributed]
People: LinkedIn profile, recent activity, company role, mutual connections, public speaking, content they've published.
Companies: What they do, size, funding, tech stack, recent news, competitors, leadership, hiring signals.
Markets: Size, growth rate, key players, trends, regulation, opportunities, threats.
Topics: Current state of the art, key concepts, recent developments, expert opinions, practical applications.
.tmp/research/ for future reference