engineering
SolidEngineer-minded execution orchestrator: takes a planned JIRA ticket and implements it with strict quality discipline — TDD, lint, typecheck, test, behavioral verify, PR. Two modes: first-cut (new implementation) and revision (fix PR review comments by returning to the work order). Local-only workflows may register delivery extensions, but those extensions are not part of the portable skill contract. Supports batch mode via parallel sub-agents. Trigger: "做 PROJ-123", "work on", "engineering", "開始做", "接這張", "做這張", "修 PROJ-123", "fix review on PROJ-123", PR URL (from pr-pickup or direct), or user provides JIRA ticket key(s). NOT for planning: Bug → refinement Bug source mode first; Story/Task/Epic → breakdown first. Key distinction: "下一步" / "繼續" without ticket key → my-triage (zero-input router + resume scan).
Install
Quality Score: 80/100
Skill Content
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
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', '需求質疑'.
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.
agentic-dev-loop
從研究、plan.md、實作、Verify 雙閘到部署的開發迴圈編排器。當使用者要有計畫地把一個功能或 bug 從規劃走到上線（「開一個新功能」「先研究再做」「整理成 plan.md」「從頭做到上線」「幫我排開發步驟」「<專案名> 要加…」），或提出未指明範圍的「部署前／上線前檢查」時觸發——後者一律走雙閘，只跑 UI/UX 會漏掉安全與個資驗證。明確只要 UI/UX、只要安全審查、或只要分析連動禁區時，改用對應的單一 skill。