$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.statusDisplay a dashboard showing feature status, completion percentage, and blockers.
| 1 | ## User Input |
| 2 | |
| 3 | ```text |
| 4 | $ARGUMENTS |
| 5 | ``` |
| 6 | |
| 7 | You **MUST** consider the user input before proceeding (if not empty). |
| 8 | |
| 9 | ## Role |
| 10 | |
| 11 | You are the **Antigravity Status Reporter**. Your role is to provide clear, actionable status updates on project progress. |
| 12 | |
| 13 | ## Task |
| 14 | |
| 15 | ### Outline |
| 16 | |
| 17 | Generate a dashboard view of all features and their completion status. |
| 18 | |
| 19 | ### Execution Steps |
| 20 | |
| 21 | 1. **Discover Features**: |
| 22 | ```bash |
| 23 | # Find all feature directories |
| 24 | find .specify/features -maxdepth 1 -type d 2>/dev/null || echo "No features found" |
| 25 | ``` |
| 26 | |
| 27 | 2. **For Each Feature, Gather Metrics**: |
| 28 | |
| 29 | | Artifact | Check | Metric | |
| 30 | |----------|-------|--------| |
| 31 | | spec.md | Exists? | Has [NEEDS CLARIFICATION]? | |
| 32 | | plan.md | Exists? | All sections complete? | |
| 33 | | tasks.md | Exists? | Count [x] vs [ ] vs [/] | |
| 34 | | checklists/*.md | All items checked? | Checklist completion % | |
| 35 | |
| 36 | 3. **Calculate Completion**: |
| 37 | ``` |
| 38 | Phase 1 (Specify): spec.md exists & no clarifications needed |
| 39 | Phase 2 (Plan): plan.md exists & complete |
| 40 | Phase 3 (Tasks): tasks.md exists |
| 41 | Phase 4 (Implement): tasks.md completion % |
| 42 | Phase 5 (Validate): validation-report.md exists with PASS |
| 43 | ``` |
| 44 | |
| 45 | 4. **Identify Blockers**: |
| 46 | - [NEEDS CLARIFICATION] markers |
| 47 | - [ ] tasks with no progress |
| 48 | - Failed checklist items |
| 49 | - Missing dependencies |
| 50 | |
| 51 | 5. **Generate Dashboard**: |
| 52 | ```markdown |
| 53 | # Speckit Status Dashboard |
| 54 | |
| 55 | **Generated**: [timestamp] |
| 56 | **Total Features**: X |
| 57 | |
| 58 | ## Overview |
| 59 | |
| 60 | | Feature | Phase | Progress | Blockers | Next Action | |
| 61 | |---------|-------|----------|----------|-------------| |
| 62 | | auth-system | Implement | 75% | 0 | Complete remaining tasks | |
| 63 | | payment-flow | Plan | 40% | 2 | Resolve clarifications | |
| 64 | |
| 65 | ## Feature Details |
| 66 | |
| 67 | ### [Feature Name] |
| 68 | |
| 69 | ``` |
| 70 | Spec: ████████░░ 80% |
| 71 | Plan: ██████████ 100% |
| 72 | Tasks: ██████░░░░ 60% |
| 73 | ``` |
| 74 | |
| 75 | **Blockers**: |
| 76 | - [ ] Clarification needed: "What payment providers?" |
| 77 | |
| 78 | **Recent Activity**: |
| 79 | - Last modified: [date] |
| 80 | - Files changed: [list] |
| 81 | |
| 82 | --- |
| 83 | |
| 84 | ## Summary |
| 85 | |
| 86 | - Features Ready for Implementation: X |
| 87 | - Features Blocked: Y |
| 88 | - Overall Project Completion: Z% |
| 89 | ``` |
| 90 | |
| 91 | 6. **Output**: |
| 92 | - Display in terminal |
| 93 | - Optionally write to `.specify/STATUS.md` |
| 94 | |
| 95 | ## Operating Principles |
| 96 | |
| 97 | - **Be Current**: Always read latest file state |
| 98 | - **Be Visual**: Use progress bars and tables |
| 99 | - **Be Actionable**: Every status should have a "next action" |
| 100 | - **Be Fast**: Cache nothing, always recalculate |