x-ipe+feature+feature-board-management

Create, update, and query feature entries in x-ipe-docs/planning/features.md.

8|2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Young-Z/X-IPE --skill x-ipe-feature-feature-board-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-ipe+feature+feature-board-management
Source: https://github.com/Young-Z/X-IPE/tree/main/.github/skills/x-ipe%2Bfeature%2Bfeature-board-management
Command: npx skills add https://github.com/Young-Z/X-IPE --skill x-ipe-feature-feature-board-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill eliminates the manual coordination required to keep the feature board in x-ipe-docs/planning/features.md up to date, ensuring a single source of truth for feature status across the lifecycle.

Core Features & Use Cases

  • Create, update, and query features on the board to reflect real-world work items.
  • Automatically apply status transitions during category-level tasks and keep task history.
  • Use Case: When a new feature is identified, create its board entry; during category closing, update its status and attach artifacts.

Quick Start

To update or query the feature board, invoke the skill with operation create_or_update_features or query_feature along with the required payload. Example: provide a feature_id and desired fields to add or modify.

Frequently Asked Questions about x-ipe+feature+feature-board-management

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

FAQPage Schema
How do I automate feature board management in markdown?

Feature board management is automated by creating, updating, and querying entries directly in the planning/features.md markdown file. This enforces lifecycle rules and maintains a single source of truth for feature status tracking.

What is the best way to track feature lifecycle transitions during project management?

Tracking feature lifecycle transitions is handled by automatically applying status updates during category-level tasks. The system maintains task history and produces a category_level_change_summary to reflect the modifications.

How do I create and update feature board entries for new work items?

To create or update feature board entries, invoke the create_or_update_features operation with a required payload containing the feature_id and desired fields. This adds or modifies the structured data model within the board.

Can I query specific features on the board without manual searching?

Yes, querying specific features is supported by invoking the query_feature operation with the required payload. This retrieves structured data directly from the x-ipe-docs/planning/features.md file.

Do I need any dependencies to use this feature board tracking automation?

No external dependencies are required to use this feature board tracking automation. It operates independently to manage the structured data model and enforce lifecycle rules within the markdown planning file.

When do I need to update the feature board during category-level workflows?

You need to update the feature board during category-level workflows when a new feature is identified or during category closing. This ensures board entries reflect real-world work items and attach necessary artifacts.