story-status-emoji

Synchronizes status emoji in Story markdown file H1 headings after workflow status changes.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill story-status-emoji-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-status-emoji
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/story-status-emoji
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill story-status-emoji-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Story markdown files can drift out of sync with their actual workflow status, making it hard to visually scan document state. This Skill keeps the H1 heading emoji of each legacy Story .md file aligned with its status field after create-story, dev-story, or code-review workflows run. ## Core Features & Use Cases - Status-Emoji Mapping: Maps workflow states (backlog, ready-for-dev, in-progress, review, done) and decision states (cancelled, superseded, split, cancelled-merged) to standard emoji in the H1 heading. - Compound Tech Debt Markers: Applies the 🟢🚧 compound marker when a done Story has pending entries in tech-debt/registry.yaml, reverting to 🟢 once all debt resolves. - Single-File and Batch Modes: Updates one Story file after a workflow status change, or batch-scans all Story files under docs/implementation-artifacts/stories to fix mismatches. - Use Case: After code-review approves Story QGR-E6 with deferred tech debt, the heading is updated from 🟠 to 🟢🚧 so the pending debt is visible at a glance. ## Quick Start Ask the AI to run the story-status-emoji skill in batch mode to synchronize all Story file heading emoji with their status fields.

Frequently Asked Questions about story-status-emoji

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

FAQPage Schema
How do I update the status emoji in a Story file heading?

Read the Story file's status field, look up the matching emoji in the mapping table, then replace the H1 heading emoji using the provided regex pattern. Workflows like create-story, dev-story, and code-review invoke this automatically after status changes.

How do I batch update emoji across all Story files?

Trigger batch mode by asking to batch update emoji or sync all status symbols. The skill globs all Story markdown files under docs/implementation-artifacts/stories, compares each heading emoji to the status field, and updates mismatches with a summary report.

Does this work for DB-first Stories without markdown files?

No, DB-first Stories are explicitly out of scope. Their status lives only in the stories.status database field with no .md mirror, so the skill is a no-op and agents should record N/A rather than creating files.

What emoji indicates a done Story with pending tech debt?

A done Story with pending tech debt uses the compound marker 🟢🚧. The skill checks tech-debt/registry.yaml for pending entries sourced from that Story, and reverts to 🟢 once all matching entries are resolved.

What happens if the heading emoji disagrees with the status field?

The status field always wins because it is the single source of truth. The skill replaces the stale heading emoji to match the status field, and the update is logged in the tracking file.