status

Generate a ticket status snapshot from index data, artifacts, and recent events.

5|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/GrinRus/ai_driven_dev --skill status-grinrus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/GrinRus/ai_driven_dev/tree/main/skills/status
Command: npx skills add https://github.com/GrinRus/ai_driven_dev --skill status-grinrus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers and product teams often struggle to quickly ascertain the current state of a ticket and locate its critical artifacts. This Skill automates a consolidated view, reducing context-switching and handoff friction.

Core Features & Use Cases

  • Generates a concise status snapshot from index data, including stage, updated timestamp, and a summary.
  • Lists artifacts, reports, next steps (AIDD:NEXT_3), open questions, risks, and checks to support handoffs and QA readiness.
  • Integrates recent events and tests logs to provide a timely activity trail for debugging and planning.

Quick Start

Generate a concise status snapshot for the active ticket showing artifacts, reports, next steps, and recent events.

Frequently Asked Questions about status

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

FAQPage Schema
How do I generate a consolidated ticket status snapshot for daily handoffs?

Generate a consolidated ticket status snapshot by reading active ticket context and aggregating index data, artifacts, and recent events. The output surfaces stage, summary, reports, next steps, open questions, risks, and checks to streamline daily handoffs.

What is the best way to summarize ticket artifacts and recent events for QA readiness?

Summarize ticket artifacts and recent events by consolidating index data and integrating test logs. This provides a timely activity trail and surfaces open questions, risks, and checks to verify QA readiness for the active ticket.

How does aggregating index data help surface ticket state and open questions?

Aggregating index data consolidates ticket state by combining updated timestamps, summaries, and artifacts. This mechanism automatically surfaces open questions and risks, reducing context-switching and handoff friction for engineering teams.

Can I refresh the index before rendering a deterministic ticket status view?

Yes, you can optionally refresh the index before rendering to support deterministic output. Reading the active ticket context after an index refresh ensures the status snapshot reflects the most current artifacts and recent events.

Does generating a ticket status report work without external dependencies?

Generating a ticket status report works without external dependencies by reading the active ticket context directly. It consolidates internal index data, artifacts, and recent test logs to produce the status snapshot autonomously.