skills.rest
l3ocho
l3ochoCOMMUNITY
Explore all skills by this author →
GitHub

input-detection

Detect and prioritize sprint planning input sources for routing to workflows.

Updated Jan 26, 2026
Search Tags:#automation#planning#wiki#rfc#input#detect
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill input-detection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: input-detection
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/input-detection
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill input-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect planning input source for sprint planning and route it to the correct workflow for RFCs, local files, wiki proposals, or conversation context.

Core Features & Use Cases

  • Detects and prioritizes input sources in the order RFCs, local files, existing wiki proposals, then conversation context.
  • Routes planning input to the appropriate workflow and surfaces clear options when multiple sources are present.
  • Use case: At sprint start, Claude Code should determine whether to use an approved RFC, a local planning file, a wiki Change Proposal, or conversation notes to seed planning.

Quick Start

Detect the planning input source for the current sprint and route it to the appropriate planning workflow.

Frequently Asked Questions about input-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect and prioritize planning inputs for sprint planning?▼

Sprint input detection scans RFCs, local files, wiki proposals, and conversation context to determine the primary planning source. It applies provenance detection and source prioritization to route inputs to the correct planning workflow.

What is the source priority order when detecting RFCs and wiki proposals for sprint planning?▼

When multiple planning sources are detected, the system prioritizes RFCs, local files, wiki proposals, and conversation context in that order. It surfaces clear options to help you choose the appropriate input for routing.

Can I use conversation context as a sprint planning input if no RFC or local file exists?▼

Yes, conversation context is supported as a fallback planning input when RFCs, local files, and wiki proposals are absent. The detection system routes conversation notes to seed sprint planning if no higher-priority source is found.

How do I route a detected RFC to the correct sprint planning workflow?▼

Once an RFC is detected as the planning input, the system automatically routes it to the appropriate sprint planning workflow. This routing logic handles source prioritization and directs RFCs to specialized planning pipelines.

What happens when multiple planning input sources like local files and wiki proposals are detected at sprint start?▼

When multiple planning inputs like local files and wiki proposals are detected simultaneously, the system surfaces clear options and applies source prioritization. It evaluates RFCs, local files, wiki proposals, and conversation context to recommend the correct routing path.

Related Skills

Explore More Product & Management Skills→
l3ochol3ocho

planning-workflow

Automate 11-step sprint planning workflows from validation through approval.

Community
Advanced
shalevaminshalevamin

sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
l3ochol3ocho

rfc-workflow

Coordinate RFC lifecycle management from proposal through implementation using a central RFC-Index.

Community
Advanced
SebastienDegodezSebastienDegodez
8

discovery-review-criteria

Review DISCOVER artifacts for completeness and prioritization quality.

Community
Advanced