メニュー
Pull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Strict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.
Strict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.
Strict red/green/refactor/simplify discipline for the `/build <task-id>` command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in `.tdd-state.json`.
JUnit 5 + Spring Boot 4 test slice patterns and Testcontainers integration test patterns with `@ServiceConnection`. Use when writing or reviewing any test, especially when choosing between unit / slice / integration scope.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles), testing, or CLI tooling.
Apply clarity-over-cleverness rewrites — prefer code a junior engineer can read at a glance over compact-but-clever code. Use during `/build`'s simplify step and during `/code-simplify` (alias "simplify the code"). Never weakens behavior; suite must remain green.
| name | issue-tracker-ingestion |
| description | Pull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket. |
| when_to_use | ["Phase 1 (Specify) — converting a tracker ID into a spec.","Verifying that a spec's `## Source` accurately reflects the ticket."] |
| authoritative_references | ["docs/platform-mapping.md (MCP wiring)",".claude/templates/spec.template.md"] |
| Source | MCP server | Identifier shape |
|---|---|---|
| Jira (Atlassian) | atlassian | SHOP-1422 |
| GitHub Issues | github | owner/repo#42 or URL |
| GitHub Pull Requests | github | owner/repo!42 or URL |
| Linear | linear | ENG-123 |
| Azure Boards | azure-devops | AB#54321 |
If no MCP is configured, fall back to user-provided text. Never invent a ticket.
Resolve identifier → MCP fetch.
Capture: title, description, status, labels, assignee, comments (last 10), attachments (filenames only), URL, fetched-at timestamp.
Write a verbatim block in 01-spec.md:
## Source
- **System:** Jira
- **ID:** SHOP-1422
- **URL:** https://example.atlassian.net/browse/SHOP-1422
- **Title:** Apply gift card at checkout
- **Status:** In Progress
- **Fetched:** 2026-04-18T10:00:00Z
### Description (verbatim)
> Users should be able to apply a gift card during checkout. It should reduce the order total. If the card has been used, show an error.
### Comments (last N, verbatim)
> [PM, 2026-04-15]: Confirmed only authenticated buyers in scope.
> [Eng lead, 2026-04-16]: Use existing error envelope.
Extract candidate ACs only from the verbatim text. Do not paraphrase requirements; quote the source line and put your AC under it. If a candidate AC has no source line, it goes to ## Open Questions as a Q-NNN.
If a source field is missing (e.g. no acceptance criteria in the ticket), the agent does not fill it from imagination. It writes:
- **Q-001** — Source ticket has no explicit acceptance criteria. Need user to confirm AC list before proceeding to AC drafting.
/spec then halts and asks the user.
If the user re-runs /spec and the ticket has changed:
## Out-of-Band Inputs ("ticket updated 2026-04-19; description gained paragraph about partial redemption").Q-NNN for any new requirement not yet in AC.