القائمة
Start work on a new ticket. Runs pre-flight checks, investigates the codebase, and flows into OpenSpec proposal. Use when the user pastes a ticket, issue, or task description.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Initialize a new project with the copilot template. Interactive setup that auto-detects the tech stack and fills in all template placeholders.
Rebuild or update the code-graph database. Use when the user wants to refresh the code graph, e.g. after major changes or when graph seems stale.
Implement tasks from an OpenSpec change. Use when the user wants to start or continue implementing a proposed change.
Archive a completed change. Use when implementation is done and the change is ready to be moved to the archive.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with specs and tasks ready for implementation.
استنادا إلى تصنيف SOC المهني
| name | new-ticket |
| description | Start work on a new ticket. Runs pre-flight checks, investigates the codebase, and flows into OpenSpec proposal. Use when the user pastes a ticket, issue, or task description. |
| argument-hint | Paste ticket description, URL, or summary |
| license | MIT |
| metadata | {"author":"copilot-template","version":"1.0"} |
Start work on a new ticket — run pre-flight, investigate, and propose a change.
Before doing anything else:
get_minimal_context with a one-line summary of the ticket. Record whether code-graph is available. If available, use it for ALL navigation in subsequent steps.openspec/changes/ (skip archive/). If an existing OpenSpec overlaps with this ticket, stop and ask: "There's an in-progress change <name> — is this ticket related, or should I start fresh?".github/copilot-instructions.md if not already loaded.Extract from the user's input:
If the ticket is vague (no specific files, unclear deliverable, touches 3+ areas), note this — it affects Step 3.
Use code-graph tools (or fallback chain) to:
Scope the investigation to the ticket. Don't audit the entire codebase.
If the ticket is vague or complex (identified in Step 2):
If the ticket is specific and well-scoped:
Once investigation is complete and requirements are clear, invoke the openspec-propose skill to create the proposal.
Pass it a clear description synthesized from the ticket + your investigation findings.
Do NOT implement anything. The propose skill will create artifacts and wait for user approval.