daily-cyclelisted

# Daily Cycle - Daily Sales Cycle Execution A skill that automatically runs a full day of sales activities. All phases are executed by sub-agents to keep the main context lightweight. **Important: Do not use `context: fork` in this skill.** Due to the one-level nesting limit for sub-agents, daily-cycle itself must run in the main context and launch each phase via the Agent tool. **Context Lightweight Rules:** - Sub-agents return **only a minimal summary (3 lines or fewer) needed for decisions** to the main context. Detailed data is stored in the DB via MCP tools (record_outreach, record_response, etc.) ## Arguments - Project ID: `$0` (required) - Outbound count: `$1` (default: 30) ## Steps ### 1. Setup First, get the exact current date, time, and day of week. Treat this result as authoritative for subsequent steps (takes priority over system date information). ```bash date '+%Y-%m-%d %H:%M (%A)' ``` Verify that the project is registered on the server: Call `mcp__plugin_lead-ace_api__list_projects` and check that `$0` appears in the list. If not found, **abort** with a message to run `/setup` first. **Compliance pre-flight.** Call `mcp__plugin_lead-ace_api__get_compliance_status`. If `ready: false`, **abort the cycle** before starting any phase — every send path will fail with HTTP 412 until the missing fields are filled, and there is no point running build-list / evaluate / outbound. Tell the user which fields are missing (from `missing`) and direct them to `fix_u