project-implement:no-interview
Same as project-implement but skips the interactive interview — auto-selects recommended answers for all interview questions. Use when the user wants to run the full project workflow without being asked clarifying questions. The interview file is still generated with auto-selected answers so downstream agents have context. Triggers on "no-interview", "skip interview", "just build it", or when the user wants a hands-off implementation run.
What this skill does
# Project Runner: No-Interview Mode
This skill runs the exact same workflow as `project-implement`, but with the interview phase
set to auto-select mode. The interviewer agent will still generate questions and pick the
best recommended answer for each one, writing a full interview transcript — but it won't
prompt the user for input.
The user's request: **"$ARGUMENTS"**
Follow every phase below in exact order. Do NOT skip phases. Do NOT move to the next phase until
the current phase is fully complete. This is expected to be a long-running process.
---
## PHASE 1: Project Setup
Create the project workspace. Do this directly (no agent needed).
1. **Check for existing projects:** Use Glob to find `projects/*/` directories. Find the highest
existing project number. If no projects exist, start at 001.
2. **Generate the project slug:** Take the user's request, extract 3-5 key words, lowercase them,
join with hyphens. Example: "build a REST API for a todo app" → "rest-api-todo-app"
3. **Create the project directory:**
```
projects/NNN-slug/
```
4. **Write `request.md`:** Save the user's full request exactly as provided:
```markdown
# Project Request
$ARGUMENTS
```
5. **Write `status.md`:** Initialize the project status tracker:
```markdown
# Project Status
## Current Phase
exploration
## Progress
- [x] Phase 1: Project Setup
- [ ] Phase 2: Exploration
- [ ] Phase 3: Interview (auto-select)
- [ ] Phase 4: Planning
- [ ] Phase 5: Milestone Creation
- [ ] Phase 6: Milestone Verification
- [ ] Phase 7: Task Creation
- [ ] Phase 8-10: Implementation Swarm
## Interview Mode
auto-select (no user interaction)
## Project Path
projects/NNN-slug/
```
6. **Tell the user** the project has been created in no-interview mode and what happens next.
**IMPORTANT — Resumability:** Before creating a new project, check if the user is referencing
an existing project. If `status.md` exists in a project folder and shows an incomplete phase,
ask the user if they want to resume that project instead of starting a new one.
---
## PHASE 2: Exploration
Launch the **pr-explorer** agent to explore the repository.
1. Use the Task tool to spawn the **pr-explorer** agent with this prompt:
```
You are the exploration agent for a project-runner workflow.
Project folder: projects/NNN-slug/
Read the request from: projects/NNN-slug/request.md
Explore the repository thoroughly and write your findings to:
projects/NNN-slug/initial-findings.md
Follow the exploration checklist in your system prompt. Be thorough.
```
2. Wait for the explorer to complete.
3. Update `status.md`: mark Phase 2 complete, set current phase to "interview".
4. Tell the user: "Exploration complete. Auto-selecting interview answers..."
---
## PHASE 3: Interview (Auto-Select)
Launch the **pr-interviewer** agent with `no-interview: true`. This still runs as a
**FOREGROUND** agent since it needs to write files, but it will NOT prompt the user.
1. Use the Task tool to spawn the **pr-interviewer** agent as a foreground agent with this prompt:
```
You are the interview agent for a project-runner workflow.
no-interview: true
Project folder: projects/NNN-slug/
Read the request from: projects/NNN-slug/request.md
Read the findings from: projects/NNN-slug/initial-findings.md
AUTO-SELECT MODE: Do NOT use AskUserQuestion. Instead, generate all interview questions
as you normally would, then select the recommended answer for each one yourself.
Write the full transcript to: projects/NNN-slug/interview.md
Follow your interview protocol but auto-select the recommended option for every question.
Mark each answer with [auto-selected] in the transcript.
```
2. Wait for the interviewer to complete.
3. Update `status.md`: mark Phase 3 complete, set current phase to "planning".
4. Tell the user: "Interview auto-completed. Creating the high-level plan..."
---
## PHASE 4: Planning
Launch the **pr-planner** agent to create the strategic plan.
1. Use the Task tool to spawn the **pr-planner** agent with this prompt:
```
You are the planning agent for a project-runner workflow.
Project folder: projects/NNN-slug/
Read all context from:
- projects/NNN-slug/request.md
- projects/NNN-slug/initial-findings.md
- projects/NNN-slug/interview.md
Create a comprehensive high-level plan and write it to:
projects/NNN-slug/plan.md
Note: The interview was conducted in auto-select mode — answers were chosen by the
interviewer agent, not the user. Use them as reasonable defaults but be aware the user
may have different preferences for some decisions.
Include: architecture, technology decisions, component breakdown, data model,
testing strategy, deployment approach. Do NOT create milestones or tasks yet.
```
2. Wait for the planner to complete.
3. Update `status.md`: mark Phase 4 complete, set current phase to "milestone-creation".
4. Tell the user: "Plan created. Breaking down into milestones and tasks..."
---
## PHASE 5: Milestone Creation
Launch the **pr-milestone-creator** agent to decompose the plan into milestones.
1. Use the Task tool to spawn the **pr-milestone-creator** agent with this prompt:
```
You are the milestone creator agent for a project-runner workflow.
Project folder: projects/NNN-slug/
Read all context from:
- projects/NNN-slug/request.md
- projects/NNN-slug/initial-findings.md
- projects/NNN-slug/interview.md
- projects/NNN-slug/plan.md
Create individual milestone files in the project folder:
- projects/NNN-slug/001-milestone-slug.md
- projects/NNN-slug/002-milestone-slug.md
- etc.
Each milestone file contains all its tasks inline. Follow the exact format from your
system prompt. Be exhaustive — every requirement must be covered. Leave no gaps.
Everything must be production-ready.
```
2. Wait for the milestone creator to complete.
3. Update `status.md`: mark Phase 5 complete, set current phase to "milestone-verification".
4. Tell the user: "Milestones created. Verifying completeness..."
---
## PHASE 6: Milestone Verification (loops until pass)
Launch the **pr-milestone-verifier** agent. If it finds issues, it fixes them and re-verifies.
1. Use the Task tool to spawn the **pr-milestone-verifier** agent with this prompt:
```
You are the milestone verifier agent for a project-runner workflow.
Project folder: projects/NNN-slug/
Read all project files including all milestone files (NNN-*.md pattern).
Verify completeness, correctness, and consistency. If you find ANY issues:
1. Fix them directly in the milestone files
2. Re-run your full verification checklist
3. Repeat until ALL checks pass
Write your verification report to: projects/NNN-slug/verification.md
The final status in verification.md MUST be "PASS".
```
2. Wait for the verifier to complete.
3. Read `verification.md` and confirm it says "PASS". If it doesn't, re-launch the verifier.
4. Update `status.md`: mark Phase 6 complete, set current phase to "task-creation".
5. Tell the user: "Milestones verified. Creating task list..."
---
## PHASE 7: Task Creation
Parse the milestone files and create tasks using the TaskCreate tool. Do this directly.
1. **Read all milestone files** from the project folder (use Glob for `projects/NNN-slug/[0-9]*.md`).
2. **Parse each milestone** to extract tasks. For each task found:
- Call `TaskCreate` with:
- `subject`: "Task N.M: [Task Title]"
- `description`: The full task description and acceptance criteria
- `activeForm`: "[Task Title] — implementing"
3. **Set up dependencies** using `TaskUpdate`:
- For each task that has dependencies, use `addBlockedBy` to reference the blocking task IDs
- Map milestone task IDs (e.g., "Task 2.3") to the TaskCreate IDs
4. **Update `status.md`:**
- Record total task coRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.