From marsai-dev-team
Development cycle state management — status reporting and cycle cancellation
npx claudepluginhub v4-company/marsai --plugin marsai-dev-teamThis skill uses the workspace's default tool permissions.
Unified skill for managing development cycle state. Provides two modes: **status** (read-only inspection) and **cancel** (state mutation with confirmation).
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Unified skill for managing development cycle state. Provides two modes: status (read-only inspection) and cancel (state mutation with confirmation).
This skill is invoked by the marsai:dev-status and marsai:dev-cancel commands. The calling command specifies the mode:
| Mode | Invoking Command | Purpose |
|---|---|---|
status | /marsai:dev-status | Read-only — display cycle metrics |
cancel | /marsai:dev-cancel [--force] | Mutating — cancel the active cycle |
The mode is determined by the argument passed from the delegating command. If no mode is provided, default to status.
Both modes read from the same state files. Check for an active cycle in this order:
docs/marsai:dev-cycle/current-cycle.jsondocs/marsai:dev-refactor/current-cycle.jsonIf neither file exists or both contain a terminal status (completed, cancelled), report that no cycle is active and exit with the appropriate "no cycle" message for the current mode.
Display the current development cycle status.
Displays:
Development Cycle Status
Cycle ID: 2024-01-15-143000
Started: 2024-01-15 14:30:00
Status: in_progress
Tasks:
Completed: 2/5
In Progress: 1/5 (AUTH-003)
Pending: 2/5
Current:
Task: AUTH-003 - Implementar refresh token
Gate: 3/10 (marsai:dev-unit-testing)
Iterations: 1
Metrics (completed tasks):
Average Assertiveness: 89%
Total Duration: 1h 45m
State file: docs/marsai:dev-cycle/current-cycle.json (or docs/marsai:dev-refactor/current-cycle.json)
No development cycle in progress.
Start a new cycle with:
/marsai:dev-cycle docs/tasks/your-tasks.md
Or resume an interrupted cycle:
/marsai:dev-cycle --resume
current-cycle.jsonCancel the current development cycle with state preservation.
| Option | Description |
|---|---|
--force | Cancel without confirmation |
--force)cancelled in state fileUnless --force is specified, display:
Cancel Development Cycle?
Cycle ID: 2024-01-15-143000
Progress: 3/5 tasks completed
This will:
- Stop the current cycle
- Save state for potential resume
- Generate partial feedback report
[Confirm Cancel] [Keep Running]
Cycle Cancelled
Cycle ID: 2024-01-15-143000
Status: cancelled
Completed: 3/5 tasks
State saved to: docs/marsai:dev-cycle/current-cycle.json (or docs/marsai:dev-refactor/current-cycle.json)
Partial report: docs/dev-team/feedback/cycle-2024-01-15-partial.md
To resume later:
/marsai:dev-cycle --resume
No development cycle to cancel.
Check status with:
/marsai:dev-status
current-cycle.jsonin_progress or similar)--force, use AskUserQuestion to get explicit user confirmation; if declined, abortstatus field in current-cycle.json to cancelled and write backdocs/dev-team/feedback/cycle-{id}-partial.md summarizing completed tasks, current progress, and reason (user-cancelled)| Command | Description |
|---|---|
/marsai:dev-cycle | Start or resume cycle |
/marsai:dev-cancel | Cancel running cycle |
/marsai:dev-status | Check current status |
/marsai:dev-report | View feedback report |
Now executing the requested mode...
Read state from: docs/marsai:dev-cycle/current-cycle.json or docs/marsai:dev-refactor/current-cycle.json