القائمة
Guided feature development — delegates to the feature-dev plugin's 7-phase workflow (explore, architect, implement, review). Use before ad-hoc builds or as pre-work before gsd-execute-phase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ops-feature-dev |
| description | Guided feature development — delegates to the feature-dev plugin's 7-phase workflow (explore, architect, implement, review). Use before ad-hoc builds or as pre-work before gsd-execute-phase. |
| argument-hint | [feature description] |
| allowed-tools | ["Skill","Agent","AskUserQuestion","TodoWrite","Read","TeamCreate","SendMessage"] |
| effort | medium |
| maxTurns | 40 |
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when
feature-dev phases fan out in parallel (e.g. explore + architect, or implement +
review). This enables:
Team setup (only when the flag is enabled, and only for genuinely parallel phases):
TeamCreate("feature-dev-lifecycle")
Agent(team_name="feature-dev-lifecycle", name="phase-explore", ...)
Agent(team_name="feature-dev-lifecycle", name="phase-architect", ...)
Steer with SendMessage / broadcast; share work via TaskCreate/TaskUpdate.
If the flag is NOT set, fall back to standard fire-and-forget subagents (the
default), or invoke /feature-dev inline via the Skill tool.
Thin router into the feature-dev companion plugin. Do not re-implement its phases here.
.planning/): optional structured alternative to jumping straight into /flow build..planning/ present): run before gsd-execute-phase when you want exploration + architecture + clarifying questions; execution still canonical via GSD./review and gsd-code-review stay canonical; feature-dev Phase 6 is available via explicit /feature-dev or auto-swap to feature-dev:code-reviewer.If $ARGUMENTS is empty, invoke /feature-dev with no args (discovery phase).
Otherwise invoke /feature-dev $ARGUMENTS via the Skill tool.
/ops:setup Step 2c or /plugin install feature-dev).feature-dev:code-*) is handled by bin/ops-suggest-specialized-agent when the plugin is present./flow build, /review, or gsd-execute-phase — it overlays them.Interactive OAuth init wizard for the multi-account Claude rotator. Walks through every account in the rotation config and, for any account missing a valid keychain token, delegates to the proven `rotate.mjs` magic-link flow (browser-driver cascade + Gmail polling), which writes the verified OAuth token to `Claude-Rotation-<key>` (key = account label or email, keychain account `$USER`). Re-runnable any time. Standalone alias of the same step inside `/ops:setup`.
Multi-account Claude Max rotator. Status, manual rotation, account list, add-account wizard, and CRS relay-pool auto-prioritization. Requires account_rotation_enabled=true in plugin settings.
Full inbox management across all channels — WhatsApp (whatsmeow bridge via mcp__whatsapp__*), iMessage (chat.db reader + AppleScript send via mcp__plugin_imessage_imessage__*), Email (Gmail MCP), Slack (MCP), Telegram (user-auth MCP), Discord (webhook + REST read), Notion (MCP — comments, mentions, assigned tasks). Scans FULL inbox (not just unread), identifies messages needing replies, archives handled conversations.
Read-only AWS account hygiene audit — security baseline, unused/orphaned resources, and cost optimization across all configured regions. Produces severity-ranked findings (CRITICAL→LOW) plus a machine-readable findings.json. Cleanup actions are always human-gated, never automatic. Use for cost reviews, security sweeps, recurring account hygiene, or "audit my AWS".
Token-efficient morning briefing. Pre-gathers all data via shell scripts, then presents a unified business dashboard with prioritized actions.
Revenue and costs tracker. AWS spend via aws ce, credits tracker, project revenue stages. Shows burn rate, runway estimate, credits expiring.