forge-explain

Explain GSD milestones, slices, and tasks by reading their ROADMAP, CONTEXT, SUMMARY, and PLAN files.

3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/vh2224/forge-agent --skill forge-explain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-explain
Source: https://github.com/vh2224/forge-agent/tree/main/skills/forge-explain
Command: npx skills add https://github.com/vh2224/forge-agent --skill forge-explain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reading and interpreting GSD artifacts can be time-consuming and error-prone; this skill explains the relationships and current state without modifying the repository.

Core Features & Use Cases

  • Reads milestone (M###), slice (S##), and task (T##) artifacts and summarizes their purpose, status, and decisions.
  • Retrieves the relevant ROADMAP, CONTEXT, and SUMMARY files to explain the artifact's context and decisions.
  • Provides a non-destructive explanation for onboarding new team members or quick project audits.

Quick Start

Explain a GSD artifact by providing its identifier (e.g., M001 or TASK-123) to generate a readable summary.

Frequently Asked Questions about forge-explain

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

FAQPage Schema
How do I explain a GSD artifact without modifying the repository?

To explain a GSD artifact without modifying the repository, provide its identifier like M001 or TASK-123. The skill reads the corresponding ROADMAP, CONTEXT, and SUMMARY files to generate a non-destructive summary of the current phase, decisions, and progress.

What is the best way to summarize milestone and slice status for project audits?

Summarizing milestone and slice status for project audits is done by reading M### and S## artifact files. The skill retrieves relevant ROADMAP, CONTEXT, and SUMMARY files to report on the artifact's purpose, status, and decisions without executing write operations.

Can I read GSD task context files for onboarding new team members?

Yes, you can read GSD task context files for onboarding new team members. The skill locates relevant TASK-###-BRIEF, CONTEXT, PLAN, and SUMMARY files to provide a non-destructive explanation of the project's current state and decisions.

How does identifying the active milestone help locate GSD artifact files?

Identifying the active milestone helps locate GSD artifact files by pinpointing the relevant M###, S##, and T## identifiers. This ensures the correct ROADMAP, CONTEXT, and SUMMARY files are read to accurately explain the artifact's current phase and progress.

What GSD file types are supported to explain project progress and decisions?

Supported GSD file types to explain project progress and decisions include M###-ROADMAP, M###-CONTEXT, M###-SUMMARY, S##-PLAN, S##-CONTEXT, S##-SUMMARY, T##-PLAN, T##-SUMMARY, and TASK-###-BRIEF, CONTEXT, PLAN, and SUMMARY files.