How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

speckit.taskstoissues - Agent

Name: speckit.taskstoissues
Author: Ngx-Workshop

Custom agent imported from Ngx-Workshop/mfe-user-journey-admin-backstage (.github/agents/speckit.taskstoissues.agent.md). Copyright stays with the author.

Repository context (Backstage workflow)

Read AGENTS.md, docs/architecture.md, docs/development.md, docs/api-contracts.md and .specify/README.md before this command. This repository uses the local Markdown workflow. When generic instructions below conflict with it, follow the local workflow: use explicit user-selected feature folders, optional research/data-model/quickstart artifacts, and evidence-based handoffs. Ordinary file edits are supported; do not require helper scripts, branch creation, agent delegation or repeated approvals. Do not overwrite an existing plan with setup-plan.sh or regenerate the maintained AGENTS.md. Treat the constitution as an adopted document, not an unfilled template. Keep stable context in docs and feature progress in specs. Creating remote issues requires a user request for that action.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

Run .specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
From the executed script, extract the path to tasks.
Get the Git remote by running:

git config --get remote.origin.url

[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL

For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.

[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL

Install speckit.taskstoissues and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "ngx-workshop-mfe-user-journey-admin-backstage-speckit-ta-81d2ef", "kind": "agent", "name": "speckit.taskstoissues", "description": "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.", "publisher": "Ngx-Workshop", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "agent-md", "github-custom-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts." ], "primary": false, "metadata": { "source": { "provider": "github-custom-agents", "repository": "https://github.com/Ngx-Workshop/mfe-user-journey-admin-backstage", "path": ".github/agents/speckit.taskstoissues.agent.md", "ref": "19b31c54d4d24b5f7cc1361016198f5346a8fa2d", "url": "https://github.com/Ngx-Workshop/mfe-user-journey-admin-backstage/blob/19b31c54d4d24b5f7cc1361016198f5346a8fa2d/.github/agents/speckit.taskstoissues.agent.md", "key": "Ngx-Workshop/mfe-user-journey-admin-backstage/.github/agents/speckit.taskstoissues.agent.md" }, "tools": [ "github/github-mcp-server/issue_write" ] }, "instructions": "## Repository context (Backstage workflow)\n\nRead `AGENTS.md`, `docs/architecture.md`, `docs/development.md`,\n`docs/api-contracts.md` and `.specify/README.md` before this command.\nThis repository uses the local Markdown workflow. When generic instructions below\nconflict with it, follow the local workflow: use explicit user-selected feature\nfolders, optional research/data-model/quickstart artifacts, and evidence-based\nhandoffs. Ordinary file edits are supported; do not require helper scripts, branch\ncreation, agent delegation or repeated approvals. Do not overwrite an existing plan\nwith setup-pl", "cost": { "context_tokens": 434 } }

speckit.taskstoissues

About

Repository context (Backstage workflow)

User Input

Outline

Install speckit.taskstoissues and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews