sasd-review

Solid

Generates a SA/SD (System Analysis / System Design) document for a JIRA ticket — a structured implementation plan produced before coding begins. Use this skill whenever the user mentions SASD, SA/SD, 寫 SA, 出 SA/SD, SA 文件, SD 文件, 架構文件, implementation plan, 系統分析, 系統設計, 技術設計, 異動範圍, dev scope, design doc, technical design, or asks to analyze what changes are needed for a ticket, plan the implementation approach, or produce a technical design document — even if they don't explicitly say "SA/SD".

Code & Development 4 stars 0 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# SA/SD Review — Design-First Gate 在寫 code 前,為 JIRA ticket 產出 System Analysis / System Design 文件,先對齊需求、 異動範圍、技術方案、task estimates 與風險。 ## Contract `sasd-review` 是 design-first gate。它產出 implementation plan,不施工、不建 branch、 不開 PR。若 ticket 已經有清楚方案,也仍需確認方向,不可直接假設。 Small change 可產 brief plan;medium scope 產 standard SA/SD;large or cross-service scope 需包含 alternatives 與 risk mitigation。 ## Reference Loading | Situation | Load | |---|---| | Any run | `sasd-review-entry-exploration-flow.md`, `workspace-config-reader.md`, `project-mapping.md`, `shared-defaults.md` | | Codebase exploration | `explore-pattern.md`, `repo-handbook.md`, `worktree-dispatch-paths.md`, `planning-worktree-isolation.md` as needed | | Document writing | `sasd-review-document-template.md`, `estimation-scale.md`, `confidence-labeling.md` | | External publish | `sasd-review-publish-flow.md`, `sasd-confluence.md`, `confluence-page-update.md`, `workspace-language-policy.md`, `external-write-gate.md` | Explore sub-agent dispatch 必須注入 `sub-agent-roles.md` 的 Completion Envelope。Planning decision 留在主 session;sub-agent 只提供 codebase impact evidence。 ## Flow 1. 讀 workspace config,解析 JIRA ticket key。 2. Fetch JIRA ticket,讀 summary、description、AC、PRD/design/API/discussion links。 3. 依 `project-mapping.md` 找 target project;找不到就問使用者。 4. 讀 requirements,列 ambiguities;不清楚的先問,不猜。 5. 依 `explore-pattern.md` 探索 codebase,取得 affected files、current architecture、risks。 6. 中大型 scope 提出 2-3 個 approach 與 trade-offs,請使用者確認 recommendation。...

Details

Author
HsuanYuLee
Repository
HsuanYuLee/polaris
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

refinement

Iteratively enriches incomplete JIRA Epics into estimation-ready, technically-validated specs. Five modes: batch readiness scan, RD discovery (Phase 0), PM elaboration (Phase 1), technical approach (Phase 2), and multi-round iteration. Phase 1 goes beyond checklist filling — it explores the codebase, hardens AC, and produces a structured artifact for downstream skills. Trigger: "refinement", "grooming", "討論需求", "需求釐清", "補完 Epic", "這張單缺什麼", "brainstorm", "方案討論", "想重構", "tech debt", "batch refinement", "sprint prep", or Epic with sparse content needing enrichment.

4 Updated 3 days ago
HsuanYuLee
AI & Automation Solid

intake-triage

批次收單排工:分析 PM 開出的一批 ticket,評估優先序,告訴 PM 哪些先做、哪些後做、哪些規格不足需補。 產出 JIRA label + comment + Slack 摘要。 觸發:「收單」、「排工」、「intake」、「這批單幫我看」、「PM 開了一堆單」、「幫我排優先」、 「intake-triage」、「triage these tickets」、「prioritize this batch」。 當使用者提供一批 ticket key 並要求排優先序時使用此 skill,不要與 /my-triage(個人每日盤點)混淆。

4 Updated 3 days ago
HsuanYuLee
AI & Automation Solid

breakdown

Universal planning skill: Bug reads ROOT_CAUSE then estimates; Story/Task/Epic explores codebase then splits into sub-tasks with estimates, and packs each sub-task into a self-contained task.md work order for engineering to consume. Also handles scope challenge (advisory mode). Trigger: 拆單, 'split tasks', 拆解, 'breakdown', 'break down', 子單, 'sub-tasks', 評估這張單, 'evaluate this ticket', 估點, 'estimate', 'scope challenge', '挑戰需求', 'challenge scope', '需求質疑'.

4 Updated 3 days ago
HsuanYuLee