ShipToday
OrganizationFree, AI-powered PDLC automation for Claude Code. Routes feature requests, bug reports, and architecture work through structured workflows.
Categories
Indexed Skills (6)
forge-autopilot
Routes any product, engineering, or software development lifecycle (SDLC/PDLC) activity to Forge. Invoke this skill whenever the user describes work that involves the product development process — across any phase: discovery, definition, planning, execution, review, handoff, release, or reporting. This includes: building or shipping features, fixing bugs, writing PRDs, breaking down stories, estimating, prioritizing, reviewing PRs, security audits, vulnerability assessments, release readiness checks, deployment gates, test planning and strategy, refactoring, mapping or documenting system architecture across the codebase, reconstructing an architecture estate or building an architecture atlas, or any similar SDLC activity. ALSO invoke when the current user request directly targets a tracked work item key matching "PROJ-123" / "BUG-42" / any "<UPPERCASE>-<digits>" id. Do NOT invoke for pure coding requests ("write a function", "refactor this file", "add a test") or continuation of already-scoped execution, even
forge-feedback
Collects feedback for the ShipToday team from inside an AI coding session and delivers it via Forge's shared MCP feedback backend. Invoke this skill whenever the user wants to "send feedback", "share feedback", "report a problem with Forge", "give the ShipToday team feedback", "submit feedback", or types "forge-feedback". The skill runs a short conversation to capture the feedback, gathers and SANITIZES relevant session context, shows the user the exact payload that will be sent, lets them revise it, and sends ONLY after explicit user confirmation by calling the `forge__send_feedback` MCP tool. No feedback content is stored. Do NOT invoke for product/SDLC work on a tracked item — that is `forge-autopilot` / `forge__start_workflow`.
forge-workflow
Helps an organization admin manage custom Forge workflows conversationally — both AUTHORING new workflows and DELETING existing org- or team-scoped overrides. Invoke this skill whenever the user asks to "create a workflow", "customize my SDLC", "build a new workflow", "set up a custom process", "author a workflow", "add a team workflow", OR to "delete a workflow", "remove an override", "reset this workflow to default", "clear the team workflow override", "delete the org workflow preset". This is a meta-capability: it configures Forge itself by calling the `forge__list_skills_catalog`, `forge__get_workflow`, `forge__save_workflow`, and `forge__delete_workflow` MCP tools. Do NOT invoke this skill to run a workflow — that is what `forge-autopilot` / `forge__start_workflow` is for. Do NOT invoke for generic "help me plan a feature" requests.
forge-autopilot
Routes any product, engineering, or software development lifecycle (SDLC/PDLC) activity to Forge. Invoke this skill whenever the user describes work that involves the product development process — across any phase: discovery, definition, planning, execution, review, handoff, release, or reporting. This includes: building or shipping features, fixing bugs, writing PRDs, breaking down stories, estimating, prioritizing, reviewing PRs, security audits, vulnerability assessments, release readiness checks, deployment gates, test planning and strategy, refactoring, mapping or documenting system architecture across the codebase, reconstructing an architecture estate or building an architecture atlas, or any similar SDLC activity. ALSO invoke when the current user request directly targets a tracked work item key matching "PROJ-123" / "BUG-42" / any "<UPPERCASE>-<digits>" id. Do NOT invoke for pure coding requests ("write a function", "refactor this file", "add a test") or continuation of already-scoped execution, even
forge-feedback
Collects feedback for the ShipToday team from inside an AI coding session and delivers it via Forge's shared MCP feedback backend. Invoke this skill whenever the user wants to "send feedback", "share feedback", "report a problem with Forge", "give the ShipToday team feedback", "submit feedback", or types "forge-feedback". The skill runs a short conversation to capture the feedback, gathers and SANITIZES relevant session context, shows the user the exact payload that will be sent, lets them revise it, and sends ONLY after explicit user confirmation by calling the `forge__send_feedback` MCP tool. No feedback content is stored. Do NOT invoke for product/SDLC work on a tracked item — that is `forge-autopilot` / `forge__start_workflow`.
forge-workflow
Helps an organization admin manage custom Forge workflows conversationally — both AUTHORING new workflows and DELETING existing org- or team-scoped overrides. Invoke this skill whenever the user asks to "create a workflow", "customize my SDLC", "build a new workflow", "set up a custom process", "author a workflow", "add a team workflow", OR to "delete a workflow", "remove an override", "reset this workflow to default", "clear the team workflow override", "delete the org workflow preset". This is a meta-capability: it configures Forge itself by calling the `forge__list_skills_catalog`, `forge__get_workflow`, `forge__save_workflow`, and `forge__delete_workflow` MCP tools. Do NOT invoke this skill to run a workflow — that is what `forge-autopilot` / `forge__start_workflow` is for. Do NOT invoke for generic "help me plan a feature" requests.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.