一键导入
speckit-taskstoissuesagent
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides Claude when building, debugging, or extending features in the AutoBidder Next.js 15 + FastAPI codebase. Use this skill whenever the user mentions adding a feature, fixing a bug, writing an API endpoint, creating a React component, working on the frontend or backend code, asking about project conventions, setting up Docker, managing environment variables, or doing anything related to AutoBidder's tech stack (Next.js, FastAPI, TanStack Query, shadcn/ui, TailwindCSS, PostgreSQL, JWT auth, Resend, Vercel, Railway). Also trigger when the user shares a file path, pastes code from the project, or asks "how does X work in this project". Always consult this skill before writing any AutoBidder code — it encodes the project's conventions and will prevent pattern drift.
Guides Claude through AutoBidder's end-to-end AI proposal generation workflow. Use this skill whenever the user wants to generate, draft, review, or refine a freelance proposal — including when they paste a job description, say "write a bid", "generate a proposal", "draft a proposal for this job", "help me respond to this posting", "what should I write for this job", or share a job URL. Also trigger when the user asks about proposal strategy, how to customize a template, or whether a job is a good fit. Even if the request seems simple ("quick proposal for this"), use this skill — it encodes AutoBidder's full quality workflow and should always be consulted when proposals are involved.
Guides Claude when managing, debugging, or improving AutoBidder's RAG knowledge base pipeline. Use this skill whenever the user mentions: "knowledge base", "RAG", "ChromaDB", "embeddings", "document upload", "retrieval", "the AI isn't using the right context", "portfolio docs", "LangChain", "chunking", "vector store", "bad proposals", or "why did it generate that". Also trigger when the user wants to upload new portfolio documents, inspect what's in the knowledge base, tune retrieval quality, debug why a proposal got irrelevant context, or rebuild/reset the vector store. Always consult this skill before touching anything in backend/app/services/knowledge_service.py or the ChromaDB collection — it encodes all ingestion, retrieval, and debugging patterns for this project.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Generate a custom checklist for the current feature based on user requirements.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
| name | speckit-taskstoissues.agent |
| description | Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"templates/commands/taskstoissues.agent.md"} |
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
.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").git config --get remote.origin.url
[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL