google-agents-cli-scaffold
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
ln-230-story-prioritizer
RICE prioritization per Story with market research. Generates consolidated prioritization table in docs/market/[epic-slug]/prioritization.md. L2 worker called after ln-220.
Full skill instructions
Evaluate Stories using RICE scoring with market research. Generate consolidated prioritization table for Epic.
Use this skill when:
Do NOT use when:
Who calls this skill:
| Parameter | Required | Description | Default |
|---|---|---|---|
| epic | Yes | Epic ID or "Epic N" format | - |
| stories | No | Specific Story IDs to prioritize | All in Epic |
| depth | No | Research depth (quick/standard/deep) | "standard" |
depth options:
quick - 2-3 min/Story, 1 WebSearch per typestandard - 5-7 min/Story, 2-3 WebSearches per typedeep - 8-10 min/Story, comprehensive researchdocs/market/[epic-slug]/
└── prioritization.md # Consolidated table + RICE details + sources
Table columns (from user requirements):
| Priority | Customer Problem | Feature | Solution | Rationale | Impact | Market | Sources | Competition |
|---|---|---|---|---|---|---|---|---|
| P0 | User pain point | Story title | Technical approach | Why important | Business impact | $XB | [Link] | Blue 1-3 / Red 4-5 |
| Tool | Purpose | Example Query |
|---|---|---|
| WebSearch | Market size, competitors | "[domain] market size 2025" |
| mcp__Ref | Industry reports | "[domain] market analysis report" |
| Linear | Load Stories | list_issues(project=Epic.id) |
| Glob | Check existing | "docs/market/[epic]/*" |
Objective: Validate input and prepare context.
Process:
Parse Epic input:
get_project(query=epic)Auto-discover configuration:
docs/tasks/kanban_board.md for Team IDCheck existing prioritization:
Glob: docs/market/[epic-slug]/prioritization.md
Create output directory:
mkdir -p docs/market/[epic-slug]/
Output: Epic metadata, output path, existing check result
Objective: Build Story queue with metadata only (token efficiency).
Process:
Query Stories from Epic:
list_issues(project=Epic.id, label="user-story")
Extract metadata only:
Filter Stories:
Build processing queue:
Output: Story queue (ID + title), ~50 tokens/Story
Objective: For EACH Story: load description, research, score RICE.
Critical: Process Stories ONE BY ONE for token efficiency!
get_issue(id=storyId, includeRelations=false)
Extract from Story:
WebSearch queries (based on depth):
"[customer problem domain] market size TAM 2025"
"[feature type] industry market forecast"
mcp__Ref query:
"[domain] market analysis Gartner Statista"
Extract:
Confidence mapping:
WebSearch queries:
"[feature] competitors alternatives 2025"
"[solution approach] market leaders"
Count competitors and classify:
| Competitors Found | Competition Index | Ocean Type |
|---|---|---|
| 0 | 1 | Blue Ocean |
| 1-2 | 2 | Emerging |
| 3-5 | 3 | Growing |
| 6-10 | 4 | Mature |
| >10 | 5 | Red Ocean |
RICE = (Reach x Impact x Confidence) / Effort
Reach (1-10): Users affected per quarter
| Score | Users | Indicators |
|---|---|---|
| 1-2 | <500 | Niche, single persona |
| 3-4 | 500-2K | Department-level |
| 5-6 | 2K-5K | Organization-wide |
| 7-8 | 5K-10K | Multi-org |
| 9-10 | >10K | Platform-wide |
Impact (0.25-3.0): Business value
| Score | Level | Indicators |
|---|---|---|
| 0.25 | Minimal | Nice-to-have |
| 0.5 | Low | QoL improvement |
| 1.0 | Medium | Efficiency gain |
| 2.0 | High | Revenue driver |
| 3.0 | Massive | Strategic differentiator |
Confidence (0.5-1.0): Data quality (from Step 3.2)
Effort (1-10): Person-months
| Score | Time | Story Indicators |
|---|---|---|
| 1-2 | <2 weeks | 3 AC, simple CRUD |
| 3-4 | 2-4 weeks | 4 AC, integration |
| 5-6 | 1-2 months | 5 AC, complex logic |
| 7-8 | 2-3 months | External dependencies |
| 9-10 | 3+ months | New infrastructure |
| Priority | RICE Threshold | Competition Override |
|---|---|---|
| P0 (Critical) | >= 30 | OR Competition = 1 (Blue Ocean monopoly) |
| P1 (High) | >= 15 | OR Competition <= 2 (Emerging market) |
| P2 (Medium) | >= 5 | - |
| P3 (Low) | < 5 | Competition = 5 (Red Ocean) forces P3 |
Output per Story: Complete row for prioritization table
Objective: Create consolidated markdown output.
Process:
Sort results:
Generate markdown:
Save file:
Write: docs/market/[epic-slug]/prioritization.md
Output: Saved prioritization.md
Objective: Display results and recommendations.
Output format:
## Prioritization Complete
**Epic:** [Epic N - Name]
**Stories analyzed:** X
**Time elapsed:** Y minutes
### Priority Distribution:
- P0 (Critical): X Stories - Implement ASAP
- P1 (High): X Stories - Next sprint
- P2 (Medium): X Stories - Backlog
- P3 (Low): X Stories - Consider deferring
### Top 3 Priorities:
1. [Story Title] - RICE: X, Market: $XB, Competition: Blue/Red
### Saved to:
docs/market/[epic-slug]/prioritization.md
### Next Steps:
1. Review table with stakeholders
2. Run ln-300 for P0/P1 Stories first
3. Consider cutting P3 Stories
| Depth | Per-Story | Total (10 Stories) |
|---|---|---|
| quick | 2-3 min | 20-30 min |
| standard | 5-7 min | 50-70 min |
| deep | 8-10 min | 80-100 min |
Time management rules:
Loading pattern:
Memory management:
Position in workflow:
ln-210 (Scope → Epics)
↓
ln-220 (Epic → Stories)
↓
ln-230 (RICE per Story → prioritization table) ← THIS SKILL
↓
ln-300 (Story → Tasks)
Dependencies:
Downstream usage:
Basic usage:
ln-230-story-prioritizer epic="Epic 7"
With parameters:
ln-230-story-prioritizer epic="Epic 7: Translation API" depth="deep"
Specific Stories:
ln-230-story-prioritizer epic="Epic 7" stories="US001,US002,US003"
Example output (docs/market/translation-api/prioritization.md):
| Priority | Customer Problem | Feature | Solution | Rationale | Impact | Market | Sources | Competition |
|---|---|---|---|---|---|---|---|---|
| P0 | "Repeat translations cost GPU" | Translation Memory | Redis cache, 5ms lookup | 70-90% GPU cost reduction | High | $2B+ | M&M | 3 |
| P0 | "Can't translate PDF" | PDF Support | PDF parsing + layout | Enterprise blocker | High | $10B+ | Eden | 5 |
| P1 | "Need video subtitles" | SRT/VTT Support | Timing preservation | Blue Ocean opportunity | Medium | $5.7B | GMI | 2 |
| File | Purpose |
|---|---|
| prioritization_template.md | Output markdown template |
| rice_scoring_guide.md | RICE factor scales and examples |
| research_queries.md | WebSearch query templates by domain |
| competition_index.md | Blue/Red Ocean classification rules |
Version: 1.0.0 Last Updated: 2025-12-23
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
Set up tracing, logging, and monitoring for deployed ADK agents across Cloud Trace, BigQuery, and third-party platforms.
Enterprise Azure infrastructure architect generating Bicep or Terraform from workload descriptions.
Plan and configure production-ready Azure Kubernetes Service clusters with Day-0 and Day-1 best practices.
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
Web search, scraping, extraction, crawling, and monitoring via ScrapeGraph AI CLI.
Skill for working with Firebase Hosting (Classic). Use this when you want to deploy static web apps, Single Page Apps (SPAs), or simple microservices. Do NOT use for Firebase App Hosting.
Deploy and manage web apps with Firebase App Hosting. Use this skill when deploying Next.js/Angular apps with backends.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Build SEO-optimized pages at scale using templates, data, and proven playbook patterns.
Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers.
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Opus.ai: Revolutionize Your Web Experience
Build a no-code AI app in minutes.
An IDE for code migration from legacy to modern frameworks through coding agents.
Automate CGI animation in live-action scenes
Branded artistic QR-code concepts
Launch a website in seconds with AI.
Streamline Your Coding Experience with AI Code Helper
Convert any screenshot or design to clean code.