From marsai-dev-team
Execute the development cycle for tasks in a markdown file
npx claudepluginhub v4-company/marsai --plugin marsai-dev-team[tasks-file] [options] [prompt]Execute the development cycle for tasks in a markdown file or from a direct prompt. ## Usage ## Arguments | Argument | Required | Description | |----------|----------|-------------| | `tasks-file` | No* | Path to markdown file with tasks (e.g., `docs/tasks/sprint-001.md`) | | `prompt` | No* | Direct instruction for what to implement (no quotes needed) | *Either `tasks-file`, `prompt`, or `--resume` is required. ## Options | Option | Description | Example | |--------|-------------|---------| | `--task ID` | Execute only specific task | `--task PROJ-123` | | `--skip-gates` | Skip spec...
Execute the development cycle for tasks in a markdown file or from a direct prompt.
/marsai:dev-cycle [tasks-file] [options] [prompt]
/marsai:dev-cycle [prompt]
| Argument | Required | Description |
|---|---|---|
tasks-file | No* | Path to markdown file with tasks (e.g., docs/tasks/sprint-001.md) |
prompt | No* | Direct instruction for what to implement (no quotes needed) |
*Either tasks-file, prompt, or --resume is required.
| Option | Description | Example |
|---|---|---|
--task ID | Execute only specific task | --task PROJ-123 |
--skip-gates | Skip specific gates | --skip-gates devops,review |
--dry-run | Validate tasks without executing | --dry-run |
--resume | Resume interrupted cycle | --resume |
When a prompt is provided without a tasks file, marsai:dev-cycle enters prompt-only mode:
# Direct prompt - no tasks file needed
/marsai:dev-cycle Implement multi-tenant support for the API
# Another example
/marsai:dev-cycle Add pagination to all list endpoints with cursor-based navigation
# Tasks file with additional context
/marsai:dev-cycle docs/tasks/sprint-001.md Focus on error handling
# Tasks file with specific guidance
/marsai:dev-cycle docs/tasks/sprint-001.md Prioritize security validations
When to use direct prompt:
When to use tasks file:
/pre-dev-* first)/marsai:dev-refactor first)CANNOT override CRITICAL gates. Provides custom context to agents.
Persistence:
custom_prompt field in docs/marsai:dev-cycle/current-cycle.json--resumePropagation: Prepended to all agent prompts in a dedicated **CUSTOM CONTEXT (from user):** section. Applies to all gates and all agent types.
Constraints:
Gate Protection:
CRITICAL: Gates 3, 6, 7 enforce mandatory requirements:
Conflict Detection:
skip (gate|test|review), bypass (threshold|check))⚠️ IGNORED: Prompt matched pattern "[name]" at "[text]" — cannot override [requirement]See marsai:dev-cycle skill's "Custom Prompt Injection" section for full validation logic.
View/modify persisted prompt:
jq '.custom_prompt' docs/marsai:dev-cycle/current-cycle.json # View
# Edit state file, then: /marsai:dev-cycle --resume
# Direct prompt - implement feature
/marsai:dev-cycle Implement multi-tenant support with organization_id in all entities
# Direct prompt - another example
/marsai:dev-cycle Add idempotency support to transaction create endpoint
# Execute all tasks from a file
/marsai:dev-cycle docs/tasks/sprint-001.md
# Execute single task
/marsai:dev-cycle docs/tasks/sprint-001.md --task AUTH-001
# Skip DevOps setup (infrastructure already exists)
/marsai:dev-cycle docs/tasks/sprint-001.md --skip-gates devops
# Validate tasks without executing
/marsai:dev-cycle docs/tasks/sprint-001.md --dry-run
# Resume interrupted cycle
/marsai:dev-cycle --resume
# Tasks file with additional context
/marsai:dev-cycle docs/tasks/sprint-001.md Prioritize error handling and use existing UserRepository interface
/pre-dev-* or /marsai:dev-refactor, or a direct promptdocs/PROJECT_RULES.md with project conventionsdocs/pre-dev/{feature}/, will be used in design phase| Gate | Skill | Description |
|---|---|---|
| 0 | marsai:dev-implementation | Implement code (TDD, single-tenant) |
| 1 | marsai:dev-devops | Create Docker/compose |
| 2 | marsai:dev-sre | Observability (health checks, logging, tracing) |
| 3 | marsai:dev-unit-testing | Unit tests with 85%+ coverage |
| 4 | marsai:dev-integration-testing | Integration tests with testcontainers |
| 5 | marsai:dev-chaos-testing | Chaos tests for failure scenarios |
| 6 | marsai:requesting-code-review | Code review (7 reviewers in parallel) |
| 7 | marsai:dev-validation | Final validation |
MANDATORY: All 8 gates execute per unit.
After final commit: marsai:dev-feedback-loop generates metrics report.
docs/marsai:dev-cycle/current-cycle.json (feature) or docs/marsai:dev-refactor/current-cycle.json (refactor)docs/dev-team/feedback/cycle-YYYY-MM-DD.md| Command | Description |
|---|---|
/marsai:dev-status | Check current cycle status |
/marsai:dev-cancel | Cancel running cycle |
/marsai:dev-report | View feedback report |
This command MUST load the skill for complete workflow execution.
Use Skill tool: marsai:dev-cycle
The skill contains the complete 8-gate workflow with:
Pass the following context to the skill:
| Parameter | Value |
|---|---|
tasks-file | First argument if it's a .md file path (e.g., docs/tasks/sprint-001.md) |
prompt | Remaining text after tasks-file and options (direct instruction) |
--task | If provided, filter to specific task ID |
--skip-gates | If provided, list of gates to skip |
--dry-run | If provided, validate only |
--resume | If provided, resume from existing state file (marsai:dev-cycle or marsai:dev-refactor) |
Argument Parsing:
.md → treat as tasks-file--*) → no tasks-fileAfter loading skill and before executing gates, you MUST ask:
AskUserQuestion:
questions:
- question: "Select execution mode for this cycle"
header: "Mode"
options:
- label: "Manual per subtask"
description: "Checkpoint after each subtask"
- label: "Manual per task"
description: "Checkpoint after each task"
- label: "Automatic"
description: "No checkpoints, run all gates"
Do not skip this. User hints ≠ mode selection. Only explicit selection is valid.
See skill marsai:dev-cycle for full details. Key rules:
--resume after any interruption