feature-help

Inspect and report the current state of active and in-progress features.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-help
Source: https://github.com/oletizi/writingcontrol.org/tree/main/.claude/skills/feature-help
Command: npx skills add https://github.com/oletizi/writingcontrol.org --skill feature-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams visualize and monitor the lifecycle of features, providing a clear view of active and in-progress work without initiating any changes.

Core Features & Use Cases

  • Feature lifecycle walkthrough: presents the defined stages from problem discovery through teardown.
  • Current state reporting: surfaces the status of active and in-progress features for quick governance.
  • Non-intrusive guidance: offers state visibility without performing work or modifying code.

Quick Start

Inspect and report the current feature pipeline and state without triggering any actions.

Frequently Asked Questions about feature-help

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

FAQPage Schema
How do I track feature lifecycle stages from definition to teardown?

Feature lifecycle tracking monitors active and in-progress features across stages from definition to teardown, presenting defined phases like setup, implementation, review, ship, complete, and teardown for full pipeline visibility.

What is feature state reporting and how does it support project governance?

Feature state reporting surfaces the current status of active and in-progress features, giving stakeholders clear visibility into progress for planning, review, and governance scenarios without triggering execution.

Can I report on in-progress features without modifying code or triggering actions?

Yes, non-intrusive feature reporting offers state visibility by inspecting the current pipeline and reporting statuses, ensuring work is monitored without performing work or modifying code.

What's the best way to visualize active features for stakeholder reviews?

Visualizing active features for stakeholder reviews is best handled by reporting the current state of in-progress work, presenting a defined workflow that tracks progress across lifecycle stages without unintended execution.

Does feature lifecycle tracking coordinate with other workflow management components?

Feature lifecycle tracking coordinates with supporting skills to present a defined workflow, tracking progress across stages like implementation and review while maintaining governance visibility across the pipeline.

When should I use a feature lifecycle walkthrough instead of direct project tracking?

Use a feature lifecycle walkthrough when stakeholders need visibility into active and in-progress stages for governance, avoiding unintended execution by inspecting and reporting state rather than triggering changes.