jumpstart-mode 1.1.13 → 1.1.14

package/.github/skills/dependency-bottleneck-detector/templates/dependency-inventory.md

@@ -0,0 +1,88 @@
+# Dependency Inventory
+
+Use this template to capture all known and suspected dependencies for a delivery engagement.
+
+---
+
+## Engagement Details
+
+| Field | Value |
+|-------|-------|
+| Engagement | |
+| Client | |
+| Pod/Team | |
+| Date Created | |
+| Last Updated | |
+
+---
+
+## Instructions
+
+1. Fill in one row per dependency at project start and during each sprint planning session.
+2. Update Status and Days Waiting at least weekly.
+3. Use the Severity column to drive prioritization and escalation decisions.
+4. Move resolved dependencies to the Resolved section at bottom.
+
+---
+
+## Active Dependencies
+
+| ID | Dependency | Category | Description | Owner | Contact | Status | Requested Date | Needed By | Days Waiting | Severity | Work Blocked | Notes |
+|:--:|------------|----------|-------------|-------|---------|--------|:--------------:|:---------:|:------------:|:--------:|-------------|-------|
+| DEP-001 | | | | | | | | | | | | |
+| DEP-002 | | | | | | | | | | | | |
+| DEP-003 | | | | | | | | | | | | |
+| DEP-004 | | | | | | | | | | | | |
+| DEP-005 | | | | | | | | | | | | |
+
+---
+
+## Column Definitions
+
+| Column | Definition |
+|--------|-----------|
+| ID | Unique identifier (DEP-NNN) |
+| Dependency | Short name (e.g., "Apigee API key", "Legal DPA sign-off") |
+| Category | One of: Infrastructure, Identity/Auth, Integration, Data, Security, Legal/Compliance, Decision, People, Procurement, Client, Vendor, Organizational |
+| Description | Detailed description of what's needed |
+| Owner | Team or org responsible for providing this |
+| Contact | Named individual (if known) |
+| Status | Not Requested / Requested / In Progress / Blocked / Resolved |
+| Requested Date | When the request was submitted |
+| Needed By | Date by which this is needed to avoid delay |
+| Days Waiting | Business days since request was submitted |
+| Severity | Critical / High / Medium / Watch |
+| Work Blocked | Sprint items or work packages that cannot proceed without this |
+| Notes | Any relevant context, ticket numbers, escalation history |
+
+---
+
+## Severity Definitions
+
+| Severity | Definition |
+|----------|-----------|
+| Critical | Blocking critical path work, team members idle, delivery date at risk |
+| High | Blocking significant work but workarounds exist temporarily |
+| Medium | Blocking specific tasks but other sprint work can proceed |
+| Watch | Not yet blocking but lead time suggests it could become a blocker |
+
+---
+
+## Resolved Dependencies
+
+| ID | Dependency | Category | Requested | Resolved | Total Wait (days) | Resolution Notes |
+|:--:|------------|----------|:---------:|:--------:|:-----------------:|------------------|
+| | | | | | | |
+
+---
+
+## Dependency Metrics
+
+| Metric | Value |
+|--------|:-----:|
+| Total active dependencies | |
+| Critical/High count | |
+| Average days waiting | |
+| Longest outstanding | |
+| Resolved this sprint | |
+| New this sprint | |

package/.github/skills/dependency-bottleneck-detector/templates/escalation-email.md

@@ -0,0 +1,155 @@
+# Escalation Email
+
+Ready-to-customize escalation message. Fill in the bracketed fields and send.
+
+---
+
+## Fields to Complete
+
+| Field | Value |
+|-------|-------|
+| Recipient | |
+| Dependency | |
+| Project | |
+| Days Waiting | |
+| Impact | |
+
+---
+
+## Choose the Right Template
+
+| Situation | Use Template |
+|-----------|-------------|
+| 3-5 days, first follow-up | A — Polite Follow-Up |
+| 5-7 days, going to their manager | B — Manager Escalation |
+| 10+ days, director level | C — Director Escalation |
+| Repeating pattern across projects | D — Pattern Escalation |
+| Client dependency overdue | E — Client Dependency Reminder |
+
+---
+
+## Template A: Polite Follow-Up
+
+**Subject:** Following up: {dependency} for {project name}
+
+Hi {name},
+
+Following up on my request from {date} regarding {specific dependency}. I wanted to check if this is something we can move forward on this week.
+
+**Context:** Our team needs this by {date} to keep our current sprint on track. The specific items waiting on this are:
+- {item 1}
+- {item 2}
+
+Is there anything I can provide to help unblock this?
+
+Thanks,
+{your name}
+
+---
+
+## Template B: Manager Escalation
+
+**Subject:** Delivery at risk — {dependency} needed from {team}
+
+Hi {manager name},
+
+I'm reaching out because our delivery team has been waiting {N} days for {dependency} from {person/team}. I originally requested this on {date} and followed up on {date}.
+
+**Why it matters:**
+- {N} team members are blocked on {specific work items}
+- If not resolved by {date}, {sprint/milestone} will be delayed by {estimate}
+- This affects our commitment to deliver {deliverable} by {date}
+
+**What we need:**
+- {Specific, actionable ask}
+
+**What I can provide:**
+- {Anything you can do to reduce their effort}
+
+Could you help us get this prioritized? Happy to join a call to provide context.
+
+Thanks,
+{your name}
+
+---
+
+## Template C: Director Escalation
+
+**Subject:** [ESCALATION] {project name} delivery at risk — {dependency}
+
+Hi {director name},
+
+I'm escalating a blocking dependency that is putting our delivery at risk. This has been outstanding for {N} business days.
+
+**Situation:**
+- {What's needed, 1-2 sentences}
+- Requested on {date} from {team/person}
+- Followed up: {dates}
+- Escalated to {manager}: {date}
+
+**Impact:**
+- {N} team members partially idle
+- {Deliverables} delayed by {estimate}
+- Client commitment for {date} at risk
+
+**Ask:**
+- {Specific resolution needed by specific date}
+
+**Options:**
+1. Preferred: {dependency resolved by date}
+2. Alternative: {workaround with tradeoff}
+3. Last resort: {descope/delay/escalate further}
+
+Available to discuss further.
+
+Regards,
+{your name}
+
+---
+
+## Template D: Pattern Escalation
+
+**Subject:** Recurring dependency pattern affecting delivery
+
+Hi {leader name},
+
+I want to flag a pattern we're seeing across engagements: {team/process} is a recurring bottleneck.
+
+**Data:**
+- Affected projects: {N}
+- Average wait time: {N} days (vs. expected {N} days)
+- Cumulative team-days lost: {estimate}
+
+**This isn't about any single request** — it's a capacity/process pattern that could benefit from a systemic fix:
+- Increased capacity in {team}
+- Self-service option for {request type}
+- Expedited path for time-critical delivery work
+- Better SLA visibility
+
+Would it be useful to discuss process improvements?
+
+---
+
+## Template E: Client Dependency Reminder
+
+**Subject:** Action needed: {dependency} for {project name}
+
+Hi {client contact},
+
+I wanted to flag that we're waiting on {dependency} from your team to continue progress on {work stream/deliverable}.
+
+**Current status:**
+- Requested on {date}
+- Needed by {date} to maintain our delivery timeline
+- Impact if delayed: {specific consequence}
+
+**What we need:**
+{Clear, specific description of the deliverable or action needed}
+
+**How to provide:**
+{Specific instructions — email to whom, upload where, format needed}
+
+Please let me know if there are any questions or if a different timeline is needed so we can adjust our plan.
+
+Thanks,
+{your name}

package/.github/skills/dependency-bottleneck-detector/templates/unblock-action-plan.md

@@ -0,0 +1,106 @@
+# Unblock Action Plan
+
+Prioritized plan to resolve current dependency blockers. Assign owners, track progress, and escalate as needed.
+
+---
+
+## Engagement: {Engagement Name}
+## Created: {Date}
+## Review Cadence: {Daily / Every 2 days}
+
+---
+
+## Priority Actions
+
+### Priority 1: {Dependency Name} [DEP-XXX]
+
+| Field | Value |
+|-------|-------|
+| Blocked Since | {date} |
+| Impact | {what's blocked, how many people, delivery risk} |
+| Strategy | {from unblock-strategies: Escalate / Parallel / Stub / Decompose / Alternative / Advance Request / Decision Forcing / Direct Contact / Scope Adjust / Risk Accept} |
+| Action Step 1 | {specific action} — Owner: {name} — By: {date} |
+| Action Step 2 | {specific action} — Owner: {name} — By: {date} |
+| Action Step 3 | {specific action} — Owner: {name} — By: {date} |
+| Success Criteria | {how do we know this is resolved?} |
+| Fallback | {what to do if primary strategy fails} |
+| Fallback Trigger | {when do we switch to fallback? Date or condition} |
+| Status | {Not Started / In Progress / Awaiting Response / Resolved} |
+
+---
+
+### Priority 2: {Dependency Name} [DEP-XXX]
+
+| Field | Value |
+|-------|-------|
+| Blocked Since | |
+| Impact | |
+| Strategy | |
+| Action Step 1 | |
+| Action Step 2 | |
+| Success Criteria | |
+| Fallback | |
+| Fallback Trigger | |
+| Status | |
+
+---
+
+### Priority 3: {Dependency Name} [DEP-XXX]
+
+| Field | Value |
+|-------|-------|
+| Blocked Since | |
+| Impact | |
+| Strategy | |
+| Action Step 1 | |
+| Action Step 2 | |
+| Success Criteria | |
+| Fallback | |
+| Fallback Trigger | |
+| Status | |
+
+---
+
+## Parallel Workarounds in Progress
+
+Work being done while dependencies are unresolved:
+
+| Workaround | Unblocks | Limitations | Rework Needed After Resolution |
+|-----------|----------|-------------|-------------------------------|
+| | | | |
+
+---
+
+## Escalation Actions Taken
+
+| Date | Dependency | Level | To Whom | Response | Next Step |
+|:----:|------------|:-----:|---------|----------|-----------|
+| | | | | | |
+
+---
+
+## Decisions Needed to Unblock
+
+| Decision | Options | Recommendation | Decision Owner | Deadline | Impact of No Decision |
+|----------|---------|----------------|----------------|:--------:|----------------------|
+| | | | | | |
+
+---
+
+## Daily Check-In Questions
+
+Use during standup or async check-in:
+
+1. Any status change on Priority 1-3 actions?
+2. Any new dependencies identified today?
+3. Any dependency about to hit escalation threshold?
+4. Are parallel workarounds still viable or creating tech debt?
+5. Do we need to adjust sprint scope based on current blockers?
+
+---
+
+## Resolution Log
+
+| Date | Dependency | Resolution | Wait Time | Lessons Learned |
+|:----:|------------|-----------|:---------:|-----------------|
+| | | | | |

package/.github/skills/design-md-auditor/README.md

@@ -0,0 +1,19 @@
+# design-md-auditor
+
+Audit frontend implementation against DESIGN.md and produce severity-ranked remediation guidance.
+
+## Typical use
+
+- PR-level design QA
+- UI consistency drift checks
+- Accessibility and responsive compliance checks
+- AI workflow UX traceability checks
+
+## Key files
+
+- [SKILL.md](./SKILL.md)
+- [references/audit-rubric.md](./references/audit-rubric.md)
+- [references/severity-model.md](./references/severity-model.md)
+- [references/ai-workflow-checks.md](./references/ai-workflow-checks.md)
+- [templates/compliance-report-template.md](./templates/compliance-report-template.md)
+- [evals/evals.json](./evals/evals.json)

package/.github/skills/design-md-auditor/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: design-md-auditor
+description: >
+  Audit frontend implementations against an existing DESIGN.md contract and
+  produce actionable compliance findings. Use this whenever the user asks for
+  UI consistency review, PR design QA, DESIGN.md compliance checks, or wants
+  severity-ranked remediation guidance across React, Vue, Angular, Svelte,
+  Power Platform, Streamlit, or HTML/CSS codebases.
+argument-hint: >
+  Optional: path to DESIGN.md, target frontend files/screens, stack, and
+  whether you want a quick check or full compliance audit.
+---
+
+# DESIGN.md Auditor
+
+Use this skill to evaluate how closely an implementation aligns with DESIGN.md and identify specific drift.
+
+## Primary Outputs
+
+1. DESIGN.md Compliance Review table
+2. Severity-ranked findings with recommended fixes
+3. Optional remediation backlog grouped by quick wins vs structural changes
+
+## Workflow
+
+1. Locate and read DESIGN.md.
+2. Identify target implementation scope (files, routes, or screenshots).
+3. Map DESIGN.md rules to audit dimensions.
+4. Evaluate visual language, layout, component behavior, AI patterns, accessibility, and responsive behavior.
+5. Record findings with severity and concrete remediation guidance.
+6. Provide a short risk summary and implementation sequence.
+
+## Audit Dimensions
+
+- Design principles and visual language
+- Layout and navigation consistency
+- Component hierarchy and behavior
+- Screen state coverage (empty/loading/error/success)
+- AI-specific patterns (citations, confidence, traceability, approvals)
+- Accessibility baseline
+- Responsive behavior
+- Anti-pattern violations
+
+Use [references/audit-rubric.md](./references/audit-rubric.md) and [references/severity-model.md](./references/severity-model.md).
+
+## Output Format
+
+Always include this table:
+
+| Area | Finding | Severity | Recommendation |
+|---|---|---:|---|
+
+Then include:
+- Top 3 risks
+- Quick wins (<= 1 day)
+- Structural fixes (> 1 day)
+
+## Resource Map
+
+- [references/audit-rubric.md](./references/audit-rubric.md)
+- [references/severity-model.md](./references/severity-model.md)
+- [references/ai-workflow-checks.md](./references/ai-workflow-checks.md)
+- [templates/compliance-report-template.md](./templates/compliance-report-template.md)
+- [evals/evals.json](./evals/evals.json)
+
+## Trigger Keywords
+
+DESIGN.md audit, design compliance review, UI drift, PR design QA, frontend consistency check, review queue design regression, RAG UI compliance.

package/.github/skills/design-md-auditor/evals/evals.json

@@ -0,0 +1,23 @@
+{
+  "skill_name": "design-md-auditor",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Audit this Vue review queue implementation against DESIGN.md and provide severity-ranked findings.",
+      "expected_output": "Compliance table with clear findings, severities, and concrete remediation guidance.",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Review this PR for DESIGN.md drift in typography, spacing, and primary action hierarchy.",
+      "expected_output": "PR-focused design QA findings with quick wins and structural fixes.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Audit a RAG chat screen for citation, confidence, and override workflow compliance.",
+      "expected_output": "AI workflow UX compliance review with risk-ranked recommendations.",
+      "files": []
+    }
+  ]
+}

package/.github/skills/design-md-auditor/references/ai-workflow-checks.md

@@ -0,0 +1,23 @@
+# AI Workflow Checks
+
+Use these checks when auditing AI-enabled screens.
+
+## Evidence Visibility
+- AI outputs link to citations or supporting sources.
+- Source metadata includes title/type/date where available.
+
+## Confidence And Quality Signals
+- Confidence indicators are understandable and contextual.
+- Low-confidence behavior is explicit.
+
+## Human Review Controls
+- Approve/reject/override actions are explicit.
+- Rationale capture is available when required.
+
+## Traceability
+- Audit records include actor and timestamp.
+- Tool call or workflow timeline is visible where applicable.
+
+## Exception Handling
+- Retrieval/tool errors are visible and recoverable.
+- No-answer behavior is explicit when evidence is insufficient.

package/.github/skills/design-md-auditor/references/audit-rubric.md

@@ -0,0 +1,40 @@
+# Audit Rubric
+
+Score each dimension as `Pass`, `Partial`, or `Fail`.
+
+## 1. Visual Language Alignment
+- Typography and color usage match DESIGN.md intent.
+- Hierarchy and density are consistent.
+
+## 2. Layout And Navigation
+- App shell, headers, panels, and route-level patterns are consistent.
+- Primary actions stay visible and predictable.
+
+## 3. Component Standards
+- Buttons, inputs, tables, cards, modals, drawers follow documented behavior.
+- No competing primary actions in the same region.
+
+## 4. State Coverage
+- Empty, loading, error, and success states are present and meaningful.
+
+## 5. AI Workflow Patterns
+- Evidence/citations visible with source metadata.
+- Confidence displayed with context.
+- Approval/override behavior auditable.
+
+## 6. Accessibility
+- Keyboard flow works for critical workflows.
+- Focus states visible.
+- Status not communicated by color alone.
+
+## 7. Responsive Behavior
+- Desktop/laptop primary path intact.
+- Tablet/mobile adaptations preserve critical actions.
+
+## 8. Anti-Pattern Violations
+- Forbidden patterns from DESIGN.md are absent.
+
+## Scoring Guidance
+- Pass: conforms to DESIGN.md with no material risk
+- Partial: minor drift or inconsistent implementation
+- Fail: material drift or user-impacting issue

package/.github/skills/design-md-auditor/references/severity-model.md

@@ -0,0 +1,33 @@
+# Severity Model
+
+Use these severity levels for compliance findings.
+
+## High
+Use when mismatch creates high workflow risk, governance risk, or major usability/accessibility failure.
+
+Examples:
+- Approval actions missing audit trail
+- Color-only status in critical workflow
+- Primary action hierarchy broken in core flow
+
+## Medium
+Use when mismatch causes noticeable friction or inconsistency without immediate critical risk.
+
+Examples:
+- Inconsistent spacing/typography hierarchy
+- Missing loading/empty states for non-critical view
+- Tablet layout hides secondary but important metadata
+
+## Low
+Use when mismatch is cosmetic or minor and does not materially affect workflow completion.
+
+Examples:
+- Minor border radius drift
+- Inconsistent icon sizing
+- Slightly off component paddings
+
+## Recommendation Format
+Each finding recommendation should include:
+1. What to change
+2. Where to change it
+3. Why it matters

package/.github/skills/design-md-auditor/templates/compliance-report-template.md

@@ -0,0 +1,23 @@
+## DESIGN.md Compliance Review
+
+| Area | Finding | Severity | Recommendation |
+|---|---|---:|---|
+| [Area] | [Finding] | [High/Medium/Low] | [Specific action] |
+
+## Top Risks
+1. [Risk]
+2. [Risk]
+3. [Risk]
+
+## Quick Wins (<= 1 day)
+- [Fix]
+- [Fix]
+
+## Structural Fixes (> 1 day)
+- [Fix]
+- [Fix]
+
+## Coverage Notes
+- DESIGN.md path:
+- Implementation scope reviewed:
+- Out-of-scope areas:

package/.github/skills/design-md-creator/README.md

@@ -0,0 +1,49 @@
+# design-md-creator
+
+Create and maintain `DESIGN.md` files as an implementation contract for frontend design intent.
+
+## What this skill is for
+
+- Generate a full `DESIGN.md` from rough notes, PRDs, screenshots, and prototype guidance.
+- Update existing `DESIGN.md` files without losing established rules.
+- Audit frontend implementations for `DESIGN.md` compliance.
+- Add AI-specific UI patterns for RAG, review queues, citations, and traceability.
+
+## Typical outputs
+
+- New `DESIGN.md`
+- Updated `DESIGN.md` patch with revision notes
+- `DESIGN.md Compliance Review` findings table
+- Optional semantic design token section
+- Optional framework implementation appendix
+
+## Skill assets
+
+- [SKILL.md](./SKILL.md)
+- [references/design-md-structure.md](./references/design-md-structure.md)
+- [references/visual-language-guide.md](./references/visual-language-guide.md)
+- [references/component-standards.md](./references/component-standards.md)
+- [references/ai-ui-patterns.md](./references/ai-ui-patterns.md)
+- [references/accessibility-rules.md](./references/accessibility-rules.md)
+- [references/responsive-design.md](./references/responsive-design.md)
+- [references/anti-patterns.md](./references/anti-patterns.md)
+- [references/framework-implementation-notes.md](./references/framework-implementation-notes.md)
+- [references/design-review-checklist.md](./references/design-review-checklist.md)
+- [references/stitch-design-md-notes.md](./references/stitch-design-md-notes.md)
+- [templates/DESIGN.enterprise-ai.md](./templates/DESIGN.enterprise-ai.md)
+- [templates/DESIGN.rag-chat.md](./templates/DESIGN.rag-chat.md)
+- [templates/DESIGN.review-queue.md](./templates/DESIGN.review-queue.md)
+- [templates/DESIGN.vue.md](./templates/DESIGN.vue.md)
+- [templates/DESIGN.react.md](./templates/DESIGN.react.md)
+- [templates/DESIGN.power-platform.md](./templates/DESIGN.power-platform.md)
+- [examples/prompts.md](./examples/prompts.md)
+- [evals/evals.json](./evals/evals.json)
+- [evals/rubric.md](./evals/rubric.md)
+- [scripts/inspect_design_md.py](./scripts/inspect_design_md.py)
+- [scripts/generate_design_review.py](./scripts/generate_design_review.py)
+
+## Quick prompt examples
+
+- Create a `DESIGN.md` for an AI-powered prior authorization review app. Style: enterprise, dark, high contrast. Stack: Vue 3 + TypeScript.
+- Update the existing `DESIGN.md` to add mobile and tablet behavior plus review queue anti-patterns.
+- Audit this React dashboard against `DESIGN.md` and produce a compliance findings table.