map

Display the plan tree of sagas, epics, and stories with build and ticketing statuses.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/weside-ai/claude-code-plugin --skill map-weside-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map
Source: https://github.com/weside-ai/claude-code-plugin/tree/main/we/skills/map
Command: npx skills add https://github.com/weside-ai/claude-code-plugin --skill map-weside-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, read-only overview of the entire plan tree, including sagas, epics, and stories, along with their build states and ticketing statuses.

Core Features & Use Cases

  • Plan Tree Overview: Display the full hierarchy of sagas, epics, and stories, with their respective statuses.
  • Status Information: Present the build state and ticketing status of each item in the plan tree.
  • Filtering: Optionally filter the view to show only specific sagas or stories.
  • Use Case: When you want to quickly assess the progress and status of all projects or a specific project within the repository.

Quick Start

Use the /we:map command to view the entire plan tree.

Frequently Asked Questions about map

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

FAQPage Schema
How do I view the entire plan tree and track project status at a glance?

To view the entire plan tree and track project status, use the /we:map command to generate a read-only overview of sagas, epics, and stories along with their current build states and ticketing statuses.

Can I filter the plan tree overview to show only specific sagas?

Yes, you can filter the plan tree overview to display only specific sagas by providing a saga slug, or filter by an exact ticket key to isolate individual stories within the repository.

How does the plan tree overview retrieve build states and ticketing statuses?

The plan tree overview retrieves build states and ticketing statuses by parsing YAML frontmatter in plan files and querying integrated ticketing tools or CI systems for real-time updates.

Does the plan tree status tracking require any specific environment setup?

Plan tree status tracking requires accessible plan files with properly formatted YAML frontmatter and potentially requires configured access to your ticketing tool or CI system to fetch live build states.

What is the best way to assess the progress of all projects in my repository?

The best way to assess the progress of all projects in your repository is to generate a read-only plan tree overview, which aggregates saga, epic, and story statuses into a single hierarchical view.

Can I modify project statuses directly from the plan tree overview?

No, the plan tree overview is strictly read-only and designed for viewing build states and ticketing statuses, meaning you cannot modify project statuses directly through this interface.