{"id":50889,"plugin_id":"plugin_asdk_app_6ac3cd66361c81918045b557462d27f4","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:44:45.965Z","digest":"92e82c57f89ca2767c32dfd47d2a2d7839bbb6dfaf11e16cef79f3d34f69d2b9","against":null,"payload":{"description":"Use when a StartupSprints founder asks to advance a mission, continue a strategy or action, choose the next useful task, resolve a blocker, or work on a strategy without a specialist workflow.","included_files":[{"relative_path":"references/mcp-workflow.md","size_in_bytes":10072},{"relative_path":"references/mission-coordination.md","size_in_bytes":4802},{"relative_path":"references/prompt-examples.md","size_in_bytes":1867}],"name":"startupsprints-strategy-execution","skill_md_contents":"---\r\nname: startupsprints-strategy-execution\r\ndescription: Use when a StartupSprints founder asks to advance a mission, continue a strategy or action, choose the next useful task, resolve a blocker, or work on a strategy without a specialist workflow.\r\n---\r\n\r\n# StartupSprints strategy execution\r\n\r\nAdvance the founder's mission by completing the next useful deliverable within the current strategy and constraints. User instructions and prior explicit approvals take precedence over recommendations.\r\n\r\nRead [MCP workflow](references/mcp-workflow.md) before startup-specific work. Use [mission coordination](references/mission-coordination.md) for selection and specialist routing; [prompt examples](references/prompt-examples.md) provide reusable entry points.\r\n\r\n## Inputs\r\n\r\nResolve the accessible startup, its confirmed mission and audience, selected action, current attempt, blockers, time/budget, founder preferences, existing work, and available capabilities. Ask only for missing facts or permissions that affect the next step; never ask the founder to type internal IDs that tools can resolve.\r\n\r\n## Read → select → act → save → review\r\n\r\n1. **Read:** Discover actual StartupSprints tools. Use `list_startups`; read `get_startup_profile`. For a requested strategy, find its returned `actionId` through `list_actions`. For “what next,” read `get_next_actions` and relevant `get_results`. Read `get_execution_brief` and `get_action_workspace` for the chosen action; read `get_distribution_kit` when needed. Keep `startupId` explicit on every startup-specific call with an all-startup connection.\r\n2. **Select:** Relate the next deliverable to the mission and the uncertainty or prerequisite it resolves. Respect the founder's selected action and the server's eligibility. The focused plan has at most three actions; respect two actions in progress and three live experiments. Missing browser capability does not alter business eligibility.\r\n3. **Act:** Produce the actual artifact, qualified evidence, repair, or operational measurement definition. Route to a relevant installed specialist when available; use the live brief and the local mission reference when it is absent. Complete independent preparation while a required decision or capability is pending. Confirm each authenticated service identity separately. Reuse a prior explicit confirmation and bounded approval; obtain any missing authorization before sending, publishing, booking, submitting, or spending.\r\n4. **Save:** When requested or included in the task, merge current work and notes using live allowed fields. Send full replacements with current `workRevision`; reread and merge conflicts, then verify persistence. Reusable asset replacements require current `expectedUpdatedAt`. Preserve legacy findings. Saving a draft never starts or completes an experiment.\r\n5. **Review:** Distinguish prepared, executed, and measured states. Compare observed evidence with the mission, success criteria, effort, window, and stop condition. Recommend one concrete next step. “Wrap up,” “done,” or “finish this task” is ambiguous: prepare a summary and clarify the intended completed/failed verdict before `record_action_result`. That call requires an explicit instruction to record actual outcomes, current `attemptNumber` and `outcomeRevision`, and only observed metrics in `measuredMetrics`. Unknown is not measured zero; never infer a usefulness vote.\r\n\r\n## Output and fallback\r\n\r\nReturn the deliverable, why it advances the mission, evidence/uncertainty, actual progress, save status, and the smallest next action. If an integration is unavailable, use another permitted route or prepare work in chat/an authorized file; never claim unavailable access or persistence.\r\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}