メニュー
Use when an AI Shipping Labs sprint member is missing a production sprint plan, or when a local markdown plan from telegram-writing-assistant or zoom-calls must be imported into the production plans API.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Foundational entrypoint for the AI Shipping Labs PRODUCTION HTTP API. Use to learn how to authenticate, where the token/config lives, how to discover the full endpoint surface via the OpenAPI spec, the safe-write protocol, and the cross-cutting surfaces — integration settings / env config, content sync, and background-task observability. For user/CRM endpoints use `ai-shipping-labs-users`; for events and workshops use `ai-shipping-labs-events`.
Run the full development loop - pick issues, implement, QA, PM review, commit, push, repeat. Works for both new features (open issues) and Playwright test implementation (needs-testing issues).
Update a member's own AI Shipping Labs sprint plan through the member Plans API. Use when a member wants to list plans, fetch one plan, download Markdown, sync a Markdown plan back to the platform, toggle progress, or edit weeks, checkpoints, deliverables, next steps, resources, and week notes through /member-api/v1 using a member-owned API key.
Use when asked to update AI Shipping Labs sprint plans from Zoom, Slack, onboarding, questionnaire, or meeting notes; add or import missing sprint plans; clean plan task formatting; or fetch/check people registered for a production event.
Use when asked to create or update an AI Shipping Labs sprint plan from a member's submitted onboarding answers, CRM/user context, or member profile; includes fetching production onboarding data, drafting a markdown plan, importing it through the production plans API, and attaching internal context to the member profile/CRM.
Create and manage AI Shipping Labs events and workshops in production. Use when asked to "create an event", "schedule a workshop", "set up an event series", "add a Zoom event", "make a recurring event", "publish a workshop", cancel/reschedule an occurrence, or bulk-create Zoom meetings for a series. Events are created via the production API; workshops are git content synced from the workshops-content repo.
| name | ai-shipping-labs-plan-import |
| description | Use when an AI Shipping Labs sprint member is missing a production sprint plan, or when a local markdown plan from telegram-writing-assistant or zoom-calls must be imported into the production plans API. |
| metadata | {"short-description":"Import AI Shipping Labs sprint plans"} |
Use the production API at https://aishippinglabs.com. The API token is in the repo .env as API_SHIPPING_LABS_API_TOKEN; never print the token.
Check these local sources for markdown plans:
~/git/telegram-writing-assistant/articles/ai-shipping-labs/plans~/git/zoom-callsPrefer the explicit markdown plan file when it exists. Interview files are supporting context, not the plan source.
Use the checked-in scripts instead of rewriting API/parsing code:
python scripts/find_missing_sprint_plans.py --sprint may-2026 --query juan
This lists sprint enrollments without plans and can include a user search result for disambiguation.
python scripts/import_sprint_plan_markdown.py \
--sprint may-2026 \
--email member@example.com \
--source ~/git/telegram-writing-assistant/articles/ai-shipping-labs/plans/YYYYMMDD_name.md \
--create-if-missing \
--dry-run
Review the dry-run shape, then repeat without --dry-run to create/update production:
python scripts/import_sprint_plan_markdown.py \
--sprint may-2026 \
--email member@example.com \
--source ~/git/telegram-writing-assistant/articles/ai-shipping-labs/plans/YYYYMMDD_name.md \
--create-if-missing
If the plan needs a concise top-level headline, pass --goal "...". Without --goal, the importer preserves an existing API goal; if there is no existing goal, it uses the markdown Summary goal.
python scripts/find_missing_sprint_plans.py --sprint may-2026 --query <name>
import_sprint_plan_markdown.py --dry-run and check counts/sections.--dry-run.GET /api/plans/<id> or by re-running the importer dry-run and checking the API response counts.The importer maps:
Summary to summary.*Focus to focus.main and focus.supportingTimeline week bullets to weeks[].checkpointsResources, Deliverables, Accountability, and Next Steps to matching API fieldsPersona, Background, Intake, Meeting Notes, Internal Recommendations, Internal Action Items, and Sources to internal interview_notesKeep member-facing plan content in the shareable sections. Internal sections should remain internal notes.