legion-cc 0.1.0

package/workflows/devops/review.md

@@ -0,0 +1,112 @@
+# Legion DevOps — Review Workflow
+
+Invoke the devops-architect agent in review mode to validate changes against architectural intent.
+
+## Prerequisites
+- Something to review: execution artifact, code changes, or explicit path
+
+## Workflow
+
+### Step 1: Initialize
+
+```bash
+node ~/.claude/legion/bin/legion-tools.cjs init devops-review $ARGUMENTS
+```
+
+Display banner:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ LEGION ► DEVOPS ► REVIEW
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### Step 2: Load Context
+
+Follow @~/.claude/legion/workflows/core/context-load.md
+
+### Step 3: Find Review Target
+
+Resolve what to review:
+1. **From $ARGUMENTS**: If a path is provided, use it as the review target
+2. **From STATE.md**: Find the latest execution artifact
+3. **Also load**: The original architect output for comparison (if in a pipeline)
+
+If nothing to review:
+```
+⚠ Nothing to review.
+
+Provide a path to review:
+  /legion:devops:review /path/to/file-or-directory
+
+Or run the execution step first:
+  /legion:devops:execute
+```
+
+### Step 4: Spawn Reviewer Agent
+
+```
+Task(
+  prompt="<legion_context>
+You are being invoked by Legion DevOps Review workflow.
+You are operating in REVIEW MODE — your task is to REVIEW, not design.
+
+## Project Context
+{compiled context summary from .codebase/ and .planning/}
+
+## Original Architecture (Reference)
+{content of architect output if available — this is what was intended}
+
+## Review Target
+{content or path of what was implemented/changed}
+
+## Current State
+{STATE.md summary}
+
+## Review Task
+{$ARGUMENTS instructions if any, or 'Review the executed changes against the original architectural intent. Check for:
+- Alignment with architecture decisions
+- Security issues or anti-patterns
+- Missing validations or error handling
+- Terraform best practices compliance
+- Naming convention adherence
+- Tag compliance
+- Secret handling correctness'}
+
+## Instructions
+- Read and follow your full agent instructions from ~/.claude/agents/devops-architect.md
+- This is a REVIEW — produce a review report, not a new architecture
+- Use MCP tools to inspect the actual state of the codebase
+- Be specific: reference file paths, resource names, line numbers
+- Classify findings: CRITICAL / WARNING / INFO / OK
+- If unsure about anything, say 'я не знаю'
+</legion_context>",
+  subagent_type="devops-architect",
+  model="sonnet",
+  description="Review: {review target description}"
+)
+```
+
+### Step 5: Process Results
+
+Capture the review report.
+
+### Step 6: Complete
+
+Follow @~/.claude/legion/workflows/core/completion.md
+
+- Save artifact as `{NNN}-review-{slug}.md`
+- Update STATE.md — this is typically the pipeline terminal step
+- Display completion:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ ✓ COMPLETE — REVIEW: {description}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Artifact: .planning/legion/devops/{NNN}-review-{slug}.md
+Findings: {N critical, M warnings, K info}
+
+Pipeline complete. Ready for new tasks:
+  /legion:devops:quick <new task>
+  /legion:devops:architect <new architecture>
+```

package/workflows/resume.md

@@ -0,0 +1,88 @@
+# Legion — Resume Workflow
+
+Restore context from a previous session and continue where you left off.
+
+## Workflow
+
+### Step 1: Initialize
+
+```bash
+node ~/.claude/legion/bin/legion-tools.cjs init resume
+```
+
+Display banner:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ LEGION ► RESUME
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### Step 2: Load State
+
+Read `.planning/legion/STATE.md`.
+
+If no state found:
+```
+⚠ No Legion state found.
+
+Nothing to resume. Start fresh:
+  /legion:devops:quick <task>
+  /legion:devops:architect <task>
+```
+STOP here.
+
+### Step 3: Load Last Session
+
+Read the latest session record from `.planning/legion/sessions/`.
+
+### Step 4: Load Full Context
+
+Follow @~/.claude/legion/workflows/core/context-load.md
+
+Read ALL context files to restore the working environment.
+
+### Step 5: Analyze Incomplete Work
+
+From STATE.md, determine:
+1. What was the last completed task?
+2. What stage is the pipeline at?
+3. Are there any PARTIAL or BLOCKED tasks?
+4. What was the user doing when they stopped?
+
+### Step 6: Display Restoration
+
+```
+◆ Restoring context...
+
+✓ STATE.md loaded
+✓ Last session: {date}
+✓ Domain: {domain}
+✓ Pipeline: {pipeline position with marker}
+✓ Last completed: {last task type} — {description}
+✓ Context loaded: {N} .codebase/ docs, {M} artifacts
+
+◆ Ready to continue.
+```
+
+### Step 7: Route to Next Action
+
+Based on state analysis:
+
+| Situation | Action |
+|-----------|--------|
+| Pipeline has next stage | Suggest `/legion:devops:{next_stage}` |
+| Execution was PARTIAL | Suggest `/legion:devops:execute --task {next_task}` |
+| Execution was BLOCKED | Display blocker, suggest resolution |
+| Pipeline complete | Suggest `/legion:devops:quick <new task>` |
+
+Display:
+```
+───────────────────────────────────────────────
+ ► Next: /legion:devops:{action}
+   {description of what's next}
+
+   Also available:
+   - /legion:status — view full state
+   - /legion:devops:quick <task> — start a new task
+───────────────────────────────────────────────
+```

package/workflows/status.md

@@ -0,0 +1,72 @@
+# Legion — Status Workflow
+
+Display current Legion state across all domains and route to next action.
+
+## Workflow
+
+### Step 1: Detect State
+
+Run:
+```bash
+node ~/.claude/legion/bin/legion-tools.cjs status
+```
+
+If the command fails or returns empty, check manually:
+1. Look for `.planning/legion/STATE.md` in current directory (walk up)
+2. If not found, display "no Legion state" message
+
+### Step 2: Display Status
+
+#### If STATE.md exists:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ LEGION ► STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Domain:     {domain}
+Stage:      {current stage}
+Pipeline:   {pipeline with current position marked}
+Last:       {last completed task description}
+Next:       {suggested next command}
+
+─── Task History ───────────────────────────────
+
+| # | Type | Description | Date | Status |
+|---|------|-------------|------|--------|
+{task history rows}
+
+─── Session ────────────────────────────────────
+
+Last active: {date and time}
+Artifacts:   {count} in .planning/legion/{domain}/
+```
+
+#### If no STATE.md found:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ LEGION ► STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+○ No Legion state found in this project.
+
+To get started:
+  /legion:devops:quick <task>     — Fast task execution with context
+  /legion:devops:build            — Scaffold project and create .codebase/ docs
+  /legion:devops:architect <task> — Start with architecture design
+```
+
+### Step 3: Route
+
+Based on current state, suggest the most appropriate next action.
+
+Pipeline routing:
+| Current Stage | Suggested Next |
+|--------------|----------------|
+| architect (done) | `/legion:devops:plan` |
+| plan (done) | `/legion:devops:execute` |
+| execute (done) | `/legion:devops:review` |
+| review (done) | `/legion:devops:quick <new task>` |
+| any (in-progress) | `/legion:resume` |
+| no state | `/legion:devops:quick` or `/legion:devops:build` |