AH
Ali Hasan
← Back to Agentic AI Architecture
Strategy Engine Feature Discovery Role: Technical Strategist

hunt-feature

Engineering Impact & Tech Trend Feature Discovery

$ invoke_subagent('hunt-feature')
Trigger Scenarios (When Needed)
  • ✓ When deciding what technical features or capabilities to build next in an existing project.
  • ✓ When seeking to elevate a portfolio project to demonstrate production-level engineering.
  • ✓ When looking to align a technical codebase with current high-demand engineering patterns.
  • ✓ When performing an objective gap analysis on a software repository.
Activation & Guardrails

Trigger: Activated when the user requests feature ideas, project enhancements, or asks what technologies to implement for maximum portfolio impact.

Execution Rules:
• Scans the project first (package.json, Dockerfile, configs) to identify stack, architecture, and current gaps.
• Checks cache: if docs/plan/features.md was updated within 7 days, prompts to reuse or refresh.
• Cites explicit external sources for every recommended feature (job posting patterns, engineering blogs, GitHub trends).
• Never recommends impractical technologies that a single developer cannot realistically deliver.
Example Prompt: "What features should I build next to demonstrate senior backend capabilities in this repo?"
Technical Architecture & Data Contracts
Execution Pattern

Repository Gap Analysis & Market Trend Cross-Matching

Context Budget

Comprehensive scanning context analyzing repo files, config manifests, and external search data.

State Management

Saves ranked recommendations and trade-off analysis to docs/plan/features.md.

Input Contracts
Repository Configuration & Source Code Structure Market Trends & Engineering Best Practices
Output Contracts
docs/plan/features.md (Top 5 Curated Feature Recommendations) Technical Gap Matrix & CV Impact Analysis
Bundled Scripts & Reference Resources

Reference Specifications (`references/`)

research-sources.md Market Research Protocol

Guidelines and source criteria for researching tech trends, engineering blogs, and market demand.

output-template.md Document Template

Standardized template for docs/plan/features.md including technical justification and implementation scope.

Executive Overview

Developers frequently build features based on intuition or basic tutorial examples, resulting in projects that fail to demonstrate production-readiness or architectural depth.

hunt-feature is a technical strategy engine that evaluates codebases through the lens of modern software engineering requirements. It audits repository structure, identifies architectural omissions (e.g., lack of distributed caching, telemetry, backpressure management, or event streaming), and recommends the top 5 highest-impact features.

3-Phase Discovery Pipeline

[Phase 1: Codebase Gap Analysis]   --> Scans package.json, Dockerfiles, and directory trees
               ↓
[Phase 2: Market Trend Research]   --> Audits tech blogs and trending open-source architectures
               ↓
[Phase 3: Ranked Feature Matrix]   --> Produces top 5 curated recommendations in docs/plan/features.md

1. Automated Gap Analysis

Before searching, hunt-feature audits the project to detect production gaps:

  • Resilience Gaps: Does the API have rate limiting, health probes, or circuit breakers?
  • Data Gaps: Are database queries indexed? Is there caching or read-replica awareness?
  • Async Gaps: Are long-running jobs executed synchronously instead of through message queues?
  • Observability Gaps: Are distributed traces (OpenTelemetry) or Prometheus metrics configured?

2. Market Trend & Engineering Alignment

The skill cross-references identified gaps with current architectural demands:

  • Event-driven architecture (NATS JetStream, Kafka, RabbitMQ).
  • Multi-region or distributed caching strategies (Redis Cluster, edge caching).
  • Strict API contract enforcement (OpenAPI / Swagger auto-generation, RFC 9457 error contracts).

The Curated Top 5 Output Matrix

hunt-feature formats all 5 recommendations into docs/plan/features.md with:

  • Technical Intent & Rationale: Why this feature elevates the system.
  • Architectural Implementation Details: The specific libraries, protocols, and design patterns required.
  • Complexity vs. Feasibility Score: Ensuring the feature is achievable without unnecessary bloat.
  • Direct Bridge to Planning: Directly prompts the developer to feed selected features into navigate-compass for immediate task decomposition.