skills.rest
saschadudkin-sketch
saschadudkin-sketchCOMMUNITY
Explore all skills by this author →
GitHub

source-command-phase-status

Identify platform-v1 phase statuses from commit analysis and documentation.

Updated Mar 28, 2026
Search Tags:#developer tool#commit analysis#implementation tracking#phase status#software progress
One-click install
npx skills add https://github.com/saschadudkin-sketch/rezidence4 --skill source-command-phase-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-phase-status
Source: https://github.com/saschadudkin-sketch/rezidence4/tree/main/.agents/skills/source-command-phase-status
Command: npx skills add https://github.com/saschadudkin-sketch/rezidence4 --skill source-command-phase-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Provides an immediate summary of which phases of the platform-v1 are implemented and what is pending.

Core Features & Use Cases

  • Status Overview: Quickly assess the current state of implementation across platform-v1 modules.
  • Committer Identification: Matches commits with their respective features in the documentation.
  • Action Plan: Recommends next steps based on pending items.

Quick Start

Execute the source-command-phase-status skill to obtain the status of platform-v1 phases.

Frequently Asked Questions about source-command-phase-status

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

FAQPage Schema
How do I check the implementation status of platform-v1 phases?▼

To check platform-v1 phase status, analyze recent commits and match them against documentation to identify implemented modules versus pending features. This provides an immediate overview of your current development progress.

What is the best way to track pending software features through commit analysis?▼

Tracking pending software features through commit analysis involves matching code commits with their corresponding features in project documentation. This approach highlights which modules remain unfinished and generates an actionable summary of next steps.

Can I get an actionable summary of next steps for incomplete development modules?▼

Yes, you can get an actionable summary of next steps for incomplete development modules by evaluating implemented versus pending features. It recommends specific actions based on the remaining items required for full feature completion.

How does commit analysis identify which platform-v1 modules are implemented?▼

Commit analysis identifies implemented platform-v1 modules by cross-referencing code commits with project documentation. This matching process maps specific code changes to their corresponding documented features to verify completion status.

Do I need any external dependencies to track software progress for platform-v1?▼

No external dependencies are required to track software progress for platform-v1. The analysis runs standalone using internal scripts to evaluate commit history and documentation directly within your environment.

Related Skills

Explore More Software Engineering Skills→
tsuna44tsuna44

xddp.fill-rulebook

Generate project-rulebook documentation from repository structure and git history.

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-audit-uat

Audit UAT and verification items across project phases using path-globs.

Community
Advanced
wise-clawwise-claw
10

trellis-finish-work

Verify task completion, archive Trellis tasks, and record session progress.

Official
Intermediate
timzaaktimzaak
64

t-run

Coordinate multi-phase software development by dispatching tasks to specialized sub-agents.

Community
Advanced