Skip to main content
roadmap-advisor Analyzes codebase and generates prioritized feature recommendations based on ISP industry best practices. Supports full audit, quick scan, and domain-specific analysis modes.
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Show prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jdeweedata/circletel --skill roadmap-advisorThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... name roadmap-advisor description Analyzes codebase and generates prioritized feature recommendations based on ISP industry best practices. Supports full audit, quick scan, and domain-specific analysis modes. version 1.0.0 author CircleTel Engineering dependencies compound-learnings, stats-tracker, error-registry
Roadmap Advisor
"Strategic feature planning informed by codebase reality and industry best practices."
A comprehensive analysis skill that examines the CircleTel platform, identifies capability gaps against ISP industry standards, and generates prioritized, actionable roadmap recommendations with effort estimates and dependencies.
Philosophy : Not every feature needs building, but every significant gap needs surfacing. Engineering time is finiteโprioritize improvements that maximize business value per hour invested.
When This Skill Activates
This skill automatically activates when you:
Need to plan the next development cycle or sprint
Want to identify missing features or capabilities
Compare CircleTel against industry standards
Prioritize technical improvements
Assess a specific domain (billing, customer experience, network, etc.)
Plan quarterly or annual product roadmaps
Evaluate build vs. buy decisions
Ask "what should we build next?" Keywords : roadmap, feature planning, what should we build, gaps, priorities, audit, capability assessment, industry comparison, strategic planning, product roadmap, feature analysis, next sprint, improvements, recommendations
Commands Command Duration Output /roadmap full15-30 min Complete platform audit across all domains /roadmap quick5-10 min Top 10 prioritized recommendations with quick wins /roadmap [domain]10-15 min Deep-dive on specific domain /roadmap compare [competitor]10-15 min Gap analysis vs competitor features /roadmap status2 min Show in-progress recommendations from specs
Available Domains Domain Focus Areas billingInvoicing, payments, dunning, reconciliation, usage-based customerSelf-service, dashboard, support, communication, onboarding networkMonitoring, diagnostics, health, SLA, uptime operationsProvisioning, activation, technician workflows, inventory analyticsReporting, forecasting, churn prediction, dashboards partnerCommission, onboarding, portal, compliance, white-label integrationCRM, accounting, provider APIs, webhooks
Core Analysis Methodology
Phase 1: Codebase Inventory (Automated) Scan and categorize existing capabilities:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ CODEBASE INVENTORY โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ โ
โ DATABASE โโโบ Count tables, analyze schema coverage โ
โ โ supabase/migrations/*.sql โ
โ โผ โ
โ API ROUTES โโโบ Categorize endpoints by domain โ
โ โ app/api/**/*.ts โ
โ โผ โ
โ SERVICES โโโบ Map service modules and capabilities โ
โ โ lib/*/*.ts โ
โ โผ โ
โ COMPONENTS โโโบ Identify UI coverage per portal โ
โ โ components/**/*.tsx โ
โ โผ โ
โ INTEGRATIONS โโโบ List external services and maturity โ
โ lib/integrations/, webhooks/ โ
โ โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Tables: Count by domain, schema completeness
API Routes: Endpoints per category, coverage gaps
Services: Business logic coverage, abstraction quality
Components: UI feature parity across portals (admin/customer/partner)
Integrations: Provider count, sync health, depth
Phase 2: Schema Analysis Understand data model completeness:
Extract table schemas from migrations
Identify relationships and foreign keys
Map tables to business domains using heuristics/domain-detection.md
Flag orphaned or incomplete tables
Phase 3: Industry Benchmark Comparison Compare against ISP standards using benchmarks/isp-industry-standard.md:
Category CircleTel Status Industry Standard Gap Score Network Monitoring Partial Real-time dashboards, alerting Medium Usage Billing Basic Usage-based, tiered, overage High Self-Service Good 90% issues resolvable Low SLA Management Missing Uptime tracking, credit automation Critical Churn Prevention Missing Predictive analytics, intervention High
โ
Complete - Full implementation
โ ๏ธ Partial - Basic implementation, gaps remain
โ Missing - No implementation
Phase 4: Gap Prioritization For each identified gap, evaluate using rubrics in rubrics/:
Factor Weight Question Business Impact 40% Revenue, efficiency, compliance (1-10) Customer Impact 30% Satisfaction, retention, NPS (1-10) Technical Enablement 20% Unlocks future features (1-10) Complexity -10% Effort, risk, dependencies (1-10)
PRIORITY = (Business ร 0.4) + (Customer ร 0.3) + (Enablement ร 0.2) - (Complexity ร 0.1)
Phase 5: Effort Estimation Apply CircleTel-calibrated estimates from heuristics/effort-calibration.md:
Size Story Points Days Description XS 1-2 0.5-1 Config change, simple UI tweak S 3-5 2-3 Single feature, API endpoint + UI M 8-13 1-2 weeks Multi-component feature, integration L 21-34 3-4 weeks New subsystem, major workflow XL 55+ 6+ weeks Platform capability, architecture change
Calibration Factor : Apply 1.2x to all estimates based on historical CircleTel data.
Phase 6: Dependency Mapping Build dependency graph to ensure valid sequencing:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ DEPENDENCY EXAMPLE โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ โ
โ SLA Tracking โโโโโ Uptime Monitoring โ
โ โ โฒ โ
โ โ โ โ
โ โผ โ โ
โ Auto Credits โโโโโ Network Health DB โโโโโ Provider API โ
โ โ
โ (Can't build SLA without uptime, can't credit without SLA) โ
โ โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Phase 7: Roadmap Generation Output structured recommendations following templates in templates/:
Executive summary with maturity scorecard
Priority tiers (Critical โ High โ Strategic)
Quick wins (<1 week items)
Dependency map
Not Recommended section with reasoning
Output Format See templates/full-audit-output.md for complete format. Key sections:
# CircleTel Roadmap Analysis
**Analysis Date** : YYYY-MM-DD
**Mode** : [Full Audit / Quick Scan / Domain: X]
**Codebase State** : X tables, Y routes, Z services
---
## Executive Summary
[2-3 paragraphs: key findings, top gaps, strategic recommendation]
### Maturity Scorecard
| Domain | Score | Industry Avg | Status |
|--------|-------|--------------|--------|
| Billing | 7/10 | 8/10 | โ ๏ธ Below |
| Customer | 8/10 | 7/10 | โ
Above |
| Network | 3/10 | 8/10 | โ Critical |
---
## Priority 1: Critical Gaps (This Quarter)
### 1.1 [Feature Name]
**Current State** : [What exists today]
**Target State** : [Industry-standard capability]
**Business Impact** : X/10 | **Customer Impact** : Y/10
**Effort** : [Size] ([points], [weeks])
**Dependencies** : [Prerequisites]
**Implementation Approach** :
1. [Database work] (database-engineer)
2. [API work] (backend-engineer)
3. [UI work] (frontend-engineer)
---
## Quick Wins (This Week)
| Feature | Effort | Impact | Owner |
|---------|--------|--------|-------|
| [Item] | XS (1d) | Medium | [Role] |
---
## Not Recommended
| Feature | Reason |
|---------|--------|
| [Feature] | [Why not now] |
CircleTel-Specific Patterns
Strength Indicators (Don't Recommend Replacing)
Coverage system : 4-layer fallback (MTN WMS โ Consumer โ Provider โ Mock)Billing automation : NetCash Pay Now + eMandate + SMS (complete)Three-context auth : Consumer/Partner/Admin separationB2B KYC workflow : 7-stage pipeline (64% complete)Admin panel : 36 sections, RBAC with 17 roles, 100+ permissions
Gap Indicators (Check First) Look for missing tables/features in these areas:
Network monitoring : No network_health, uptime_logs, provider_statusSLA management : No sla_violations, service_creditsUsage tracking : Basic usage_history, no real-time or alertsChurn : No churn_predictions, at_risk_customersKnowledge base : No kb_articles, faq_categories
Load-Bearing Code (Be Conservative) Require extra caution when recommendations touch:
lib/supabase/server.ts - All server-side DB accesslib/coverage/aggregation-service.ts - Revenue-critical coveragecomponents/providers/*AuthProvider.tsx - Auth state managementapp/api/webhooks/**/*.ts - Payment and integration flows
Estimation Calibration Use these CircleTel benchmarks for comparison:
Feature Type Example Typical Effort New DB table + API + UI Dashboard tab M (13 pts) New integration Clickatell SMS S-M (5-8 pts) New admin section Workflow orchestration L (21 pts) New customer feature Usage alerts M (8-13 pts) Platform capability Network monitoring XL (55+ pts)
RSI Integration This skill integrates with the RSI (Recursive Self-Improvement) system:
Learning from Corrections โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ RSI FEEDBACK LOOP โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ โ
โ GENERATE ROADMAP โโโบ USER REVIEWS โโโบ CORRECTION? โ
โ โ โ
โ NO YES โ
โ โ โ โ
โ โผ โผ โ
โ SUCCESS STORE CORRECTION โ
โ (stats-tracker) (compound-learnings) โ
โ โ โ
โ โผ โ
โ UPDATE HEURISTICS โ
โ (extracted-rules/) โ
โ โ โ
โ IMPROVED FUTURE โโโโโโโโโโโโโโโโโโโโโโโ โ
โ RECOMMENDATIONS โ
โ โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Correction Types Type Example Learning Priority Override "SLA should be P2, not P1" Adjust scoring weights Effort Correction "This took 3 weeks, not 1" Calibrate estimates Missing Dependency "Needed X before Y" Add dependency rule Invalid Recommendation "We already have X" Improve inventory scan Business Context "Can't do X due to regulation" Add constraint
When corrected, store the learning in:
corrections/roadmap/YYYY-MM-DD_description.mdExtract rules to extracted-rules/ for future runs
Stats Tracking Track these metrics via stats-tracker:
Activation count per mode (full/quick/domain)
Recommendation acceptance rate
Correction rate
Most common domains analyzed
Average analysis duration
Validation Checklist After generating a roadmap:
Best Practices
Verify Before Recommending : Always check docs/architecture/SYSTEM_OVERVIEW.md and Supabase tables before claiming something is missing
Contextualize Effort : Reference similar completed work for calibration (check recent commits)
Consider Constraints : Note regulatory (RICA, POPIA), resource, and technical constraints
Balance Innovation vs Stability : Don't recommend changing load-bearing systems unless gap is critical
Include Quick Wins : Every analysis should have 2-3 items achievable in <1 week
Link to Specs : Reference existing Agent-OS specs in agent-os/specs/ when relevant
Document Trade-offs : Explain why recommendation A over alternative B
Update on Corrections : When corrected, store learning for future analyses
Related Skills
refactor - For code quality analysis within existing featuresquality-gates - For evaluating output quality of specific documentscompound-learnings - For storing corrections and extracted rulesstats-tracker - For tracking skill effectiveness metricserror-registry - For linking gaps to known recurring issues
Version : 1.0.0
Last Updated : 2026-02-12
Maintained By : CircleTel Engineering
Based On : ISP Industry Best Practices + CircleTel Operational Knowledge
More from this repository Generate and edit images using OpenAI's gpt-image models (gpt-image-1 / gpt-image-2). Use as an alternative to the Gemini (Nano Banana) image path when the user asks for OpenAI image generation, or when comparing providers for a hero/product/social asset. Covers text-to-image, image editing, transparent backgrounds, and CircleTel brand context.
Generate images cost-effectively via OpenRouter (Seedream 4.5, FLUX.2, Recraft V4, etc.) as a cheaper alternative to OpenAI gpt-image. Use when the user wants low-cost image generation, a specific OpenRouter image model, or quality comparable to gpt-image-2 at a fraction of the price. Requires OPENROUTER_API_KEY in .env.local.
Filter and browse supplier catalogues (Scoop, Miro, Nology) to identify product candidates for CircleTel portfolio
Related occupations SOC
Based on SOC occupation classification
