skills.rest
Chulf58
Chulf58COMMUNITY
Explore all skills by this author →
GitHub

forge:planned

Aggregate and display FORGE planned items from board data.

1|Updated Apr 14, 2026
Search Tags:#planning#backlog#sprint#task-tracking#board#planned
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-planned
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge:planned
Source: https://github.com/Chulf58/FORGE/tree/main/skills/planned
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-planned

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear view of FORGE planned work, helping teams quickly understand upcoming tasks and the sprint backlog.

Core Features & Use Cases

  • Retrieve planned items from the sprint board using forge_read_board or by parsing the .pipeline/board.json to read the planned array.
  • Display items grouped by status: [planned], [in-progress], [done], with the title truncated to 80 characters and the module assignment.
  • Sort items so in-progress come first, then planned, then done.
  • Useful for sprint planning reviews, backlog grooming, and status reporting.

Quick Start

Show me the current FORGE sprint backlog.

Frequently Asked Questions about forge:planned

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

FAQPage Schema
How do I view planned sprint backlog items from a FORGE board?▼

To view planned sprint backlog items, you can retrieve and display the planned array from board data using forge_read_board or by parsing the .pipeline/board.json file to aggregate upcoming tasks.

What is the best way to track sprint progress for daily standups?▼

Tracking sprint progress for standups is done by reading board data and grouping items by status: in-progress items appear first, then planned, then done, with titles truncated to 80 characters.

Can I parse board.json directly for backlog grooming without external dependencies?▼

Yes, you can parse the .pipeline/board.json file directly to read the planned array for backlog grooming. This approach requires no external dependencies to aggregate and display sprint items.

How are planned tasks sorted and displayed for sprint planning reviews?▼

Planned tasks are sorted for sprint planning reviews by prioritizing in-progress items first, followed by planned items, then done items, showing per-item status, 80-character titles, and module assignment.

Does the planned items view enforce any limitations on task title length?▼

Yes, the planned items view enforces a display limitation where task titles are truncated to 80 characters. This ensures consistent formatting when grouping items by status for progress reporting.

Related Skills

Explore More Software Engineering Skills→
Chulf58Chulf58

forge:health

Aggregate FORGE board health signals into severity-grouped reports.

Community
Intermediate
abdullah1854abdullah1854
1

daily-standup

Generate daily standup reports with Yesterday, Today, and Blockers sections.

Community
Basic
DicklesworthstoneDicklesworthstone
70

agent-fungibility

Coordinate interchangeable agents through bead-driven task plans in multi-agent workflows.

Community
Basic
expanso-ioexpanso-io

expanso-content-splitting

Split batch payloads into individual messages with Kafka and file-based DLQ routing.

Official
Intermediate