القائمة
Development cycle state management — status reporting and cycle cancellation
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | marsai:cycle-management |
| description | Development cycle state management — status reporting and cycle cancellation |
| trigger | - User wants to check the status of a running development cycle - User wants to cancel an active development cycle - Invoked by /marsai:dev-status or /marsai:dev-cancel commands |
| skip_when | - No development cycle is active or was recently started - User is asking about general project status (not cycle-specific) |
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
Main orchestrator for the 8-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation → devops → SRE → unit testing → integration testing (write) → chaos testing (write) → review → validation gates (Gates 0-7), with state persistence and metrics collection. Gates 4-5 (integration/chaos) write and update test code per unit but only execute tests at end of cycle (deferred execution). Multi-tenant dual-mode is implemented during Gate 0 and verified at Gate 0.5G (no separate post-cycle step).
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
Gate 5 of development cycle - ensures chaos tests exist using Toxiproxy to verify graceful degradation under connection loss, latency, and partitions.
Gate 1 of the development cycle. Creates/updates Docker configuration, docker-compose setup, and environment variables for local development and deployment readiness.
Gate 4 of development cycle - ensures integration tests pass for all external dependency interactions using real containers via testcontainers.
Gate 4 of development cycle - dispatches 7 specialized reviewers (code, business-logic, security, test, nil-safety, consequences, dead-code) in parallel for comprehensive code review feedback.