using-featureforge

Route conversations to the correct Skill or workflow stage and load its instructions into context.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dmulcahey/featureforge --skill using-featureforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-featureforge
Source: https://github.com/dmulcahey/featureforge/tree/main/skills/using-featureforge
Command: npx skills add https://github.com/dmulcahey/featureforge --skill using-featureforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps start conversations by routing to the correct Skill or workflow stage before any response, clarification, or action, ensuring the user prompt is handled by the appropriate runtime path.

Core Features & Use Cases

  • Determine the active Skill or workflow stage at session start and when multi-skill contexts exist.
  • Load the chosen Skill's instructions into the runtime context to guide subsequent actions.
  • Standardize interactive user-grounding: re-ground the user with a structured question format when context is split across sessions.

Quick Start

Begin every new interaction by invoking this skill to determine the correct Skill or workflow stage and load it into context.

Frequently Asked Questions about using-featureforge

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

FAQPage Schema
How do I route a conversation to the correct workflow before generating a response?

Route conversations by invoking the skill at session start to determine the correct workflow stage and preload its instructions into context before any response or action is taken.

What is the best way to load skill instructions into context for multi-skill planning?

The best way to load instructions is to apply context-loading during multi-skill planning, which resolves the active root skill and injects its frontmatter-defined execution instructions into the runtime.

How do I determine the active root skill at the start of a new session?

Determine the active root skill by evaluating the user prompt at session start, using the frontmatter-defined name and description to discover and resolve the correct runtime path.

Can I standardize user grounding when a conversation is split across multiple sessions?

Yes, you can standardize user grounding by re-grounding the user with a structured question format whenever the conversation context is split across sessions.

Do I need frontmatter metadata to enable skill discovery for context routing?

Yes, frontmatter metadata is required, specifically the defined name and description fields, because they are necessary for skill discovery and to resolve the active root skill in the runtime.