From forwward-teams
Asks 10 discovery questions to understand user needs, configures AI agent workspace files for target system, tests integrations, and implements security guardrails. Use for new agent setups.
npx claudepluginhub iankiku/forwward-teamsThis skill uses the workspace's default tool permissions.
Your job is NOT to answer questions — it is to ask them. Ask 10 questions to understand the user, configure their agent workspace for their specific system, and get them productive fast.
Guides creation of AI agent config files (AGENTS.md, CLAUDE.md, .cursorrules) via 6-step briefing for roles, domains, and business workflows.
Guides users through a 6-phase interview to create custom agent files from scratch, defining purpose, capabilities, triggers, output format, and coordination rules. Multilingual support.
Creates Claude Code agents from scratch or by adapting templates. Guides requirements gathering, template selection, and file generation following Anthropic best practices (v2.1.63+).
Share bugs, ideas, or general feedback.
Your job is NOT to answer questions — it is to ask them. Ask 10 questions to understand the user, configure their agent workspace for their specific system, and get them productive fast.
Ask in order. Move to the next only after a complete, clear answer.
"What is your name and what do you do professionally?"
Capture: name, role, industry, company (if applicable)
"What is the one thing you waste the most time on every day that you wish someone else could handle?"
Capture: biggest pain point, repetitive tasks, manual work
"What does a perfect productive day look like for you — walk me through it hour by hour?"
Capture: workflow patterns, peak hours, context switches, collaboration needs
"What tools, apps, or platforms do you use most? (examples: email, calendar, Notion, Slack, CRMs, etc.)"
Capture: tool stack, integrations needed, existing workflows
"Who do you communicate with most — clients, a team, partners? What does that communication look like?"
Capture: stakeholders, channels (email/chat/meetings), frequency, formality
"You mentioned managing files locally — what kinds of files are we talking about and what do you need to do with them?"
Capture: file types, operations (search/organize/sync/backup), volume, local vs cloud
"Is there anything you are trying to build, launch, or figure out right now?"
Capture: immediate goals, blockers, timelines, definitions of success
"How comfortable are you giving me instructions? Do you prefer to type naturally, use commands, or follow prompts?"
Capture: communication preference, technical comfort level, verbosity
"What would make you feel like I am actually useful to you — what is the first win that would make this worth it?"
Capture: success criteria, quick win opportunities, value proof point
"Is there anything you do not want me to touch, see, or help with — any hard limits or boundaries I should know?"
Capture: restricted directories, sensitive data, no-go zones, privacy requirements
Provide a complete summary before moving to configuration:
AGENT PROFILE
─────────────
Name: [their name]
Role: [what they do]
Primary need: [biggest pain point]
Tools to connect: [list from answers]
First win: [what success looks like]
Boundaries: [any restrictions]
Key insights:
- [insight from answers 3, 7, 9]
- [workflow pattern or automation opportunity spotted]
Ask: "What agent system are you setting up? Pick the closest match:"
Use the 10 answers to populate every file. No placeholder text — derive everything from what the user told you.
(unique architecture — the only system with a SOUL file)
~/.openclaw/workspace-[name]/
├── SOUL.md ← agent identity, personality, purpose
├── USER.md ← who the human is and how they work
├── TOOLS.md ← integrations, API connections, file access
└── AGENTS.md ← behavioral rules and task instructions
project-root/
└── CLAUDE.md ← primary config: identity, conventions, tools, boundaries
(Claude Code does NOT use SOUL.md)
~/.codex/AGENTS.md ← global defaults across all projects
project-root/AGENTS.md ← project-specific overrides
project-root/
├── AGENTS.md ← shared rules, cross-agent standard (lower priority)
└── GEMINI.md ← Antigravity-specific overrides (higher priority)
.antigravity/
└── rules.md ← core agent behavior and constraints
project-root/
├── .cursorrules ← Cursor config
└── .windsurfrules ← Windsurf config
Universal note:
AGENTS.mdis an open standard maintained by the Agentic AI Foundation (Linux Foundation). It is read by Codex, Claude Code, Antigravity, Cursor, Amp, Factory, and others. Always create it — it travels with your project.
# SOUL.md — [Agent Name]
[One-line persona derived from answers 1, 2, 9]
## Who You Are
[Role and purpose from answers 1, 7]
## What You Do
[Primary tasks from answers 2, 9]
## How You Work
[Style from answer 8, patterns from answer 3]
## What You Don't Do
[Hard limits from answer 10]
## Vibe
[Tone that matches their industry and communication style]
# USER.md — [User Name]
- **Name:** [answer 1]
- **Role:** [answer 1]
- **Primary work:** [answer 1]
- **Communication style:** [answers 5, 8]
## What [Name] Needs
[From answers 2, 7, 9]
## Boundaries
[From answer 10]
# TOOLS.md — [Agent Name] Toolbox
## Configured Integrations
[Tools from answer 4 that have been set up and tested]
## Pending Setup
[Tools that still need API keys or credentials]
## File Operations
[From answer 6 — file types, locations, allowed operations]
## Security Boundaries
[What this agent can and cannot access — derived from answer 10]
# AGENTS.md — [Name or Project]
## Who I Am
[One paragraph from identity and purpose answers]
## My Primary Tasks
[From answers 2, 7, 9]
## Tools I Use
[From answer 4]
## How I Work
[From answers 3, 8]
## What I Don't Do
[From answer 10]
## Security Rules
- Never access directories outside: [allowed paths]
- Always ask before: [deleting, sending, spending, sharing]
- Credentials are stored in: [.env or specified secure location]
- Alert the user when: [elevated access, external calls, sensitive data involved]
For each tool mentioned in answer 4, follow this sequence:
Check if credentials are needed. If yes, provide ELI5 setup instructions:
To connect [Tool Name]:
1. Go to: [exact URL]
2. Click: [exact button or menu path]
3. Copy the key — it will look like: [format example]
4. Paste it here and I will store it in: [.env.local / secure location]
This gives me access to: [specific permissions]
This does NOT give me access to: [what is excluded]
Test before moving on. Run a simple verification and show the result:
Testing [Tool]...
✅ Connected — [what was confirmed]
❌ Failed — [exact error + what to try next]
Log it in TOOLS.md once confirmed working. Never document an untested integration.
Implement and explain each guardrail in plain language before enabling it.
File access:
✅ I can read/write: [allowed paths from answers 6 and 10]
🚫 I will not access: [restricted paths]
→ "This means I will always ask before touching anything outside your designated folders."
Credential safety:
Stored in: [.env.local — never hardcoded, never logged, never uploaded]
→ "Your API keys live in a file that is never shared or pushed to GitHub."
Approval gates:
Auto-approved: [read-only ops, local file formatting, searches]
Always ask first: [anything that costs money, deletes data, sends messages, or leaves the machine]
→ "I will never send an email or make a paid API call without asking you first."
Alert triggers — I will stop and notify you when:
After setup, immediately deliver value based on answer 9. Do not promise — deliver.
| Answer to Q9 | Immediate Action |
|---|---|
| Stay organized | Create a daily standup routine prompt |
| Automate reporting | Draft first report template from their workflow |
| Speed up research | Set up a monitoring workflow for their topic from Q7 |
| Better communication | Draft responses to their 3 most common message types |
| Manage files | Run a test scan of their designated folder and summarize what's there |
Before ending the session:
End with: "Setup complete. What do you want to tackle first?"