Skip to content

Milestones

List view

  • Dev Container Support

    Optional project-provided dev containers alongside Skiff, giving agents a tight edit-build-test-iterate loop. See docs/superpowers/specs/2026-04-17-dev-container-support-design.md

    No due date
    •7/7 issues closed
    100% complete0 open7 closed

  • Workflow Graph v2 — Bridge Actions & Minimal Prompts

    Evolve the workflow engine from strict DAG to a workflow graph with bounded cycles and bridge actions. Agent prompts drop from ~4000 words to ~50 by moving infrastructure concerns into deterministic platform code. Design spec: docs/superpowers/specs/2026-04-14-workflow-graph-v2-design.md

    No due date
    •4/4 issues closed
    100% complete0 open4 closed

  • Agent Orchestration: Multi-Step Workflows

    ## Overview Add a lightweight orchestration layer to Alcove for coordinating multiple agents across repos, systems, and time. Uses GitHub Actions-inspired YAML syntax with execution backed by existing Alcove infrastructure (Skiff containers, NATS, PostgreSQL). No new dependencies. No Temporal Server. No Argo CRDs. Just YAML + Go code in Bridge. ## Architecture Each workflow step is a standard Alcove session (Skiff container). Bridge evaluates the DAG, dispatches steps when dependencies are met, passes outputs between steps, and handles failures and approvals. ## YAML Syntax \`\`\`yaml name: Feature Delivery Pipeline workflow: - id: implement agent: autonomous-developer repo: pulp/pulp_python trigger: github: events: [issues] labels: [ready-for-dev] outputs: [pr_url, summary] - id: deploy-staging agent: deploy-agent needs: [implement] condition: "steps.implement.outcome == 'completed'" inputs: context: "{{steps.implement.outputs.summary}}" - id: verify agent: smoke-test needs: [deploy-staging] - id: promote-prod agent: deploy-agent needs: [verify] approval: required \`\`\` ## Agent Interface Contract Agents participate in workflows by: 1. Accepting context via env vars or a JSON file 2. Producing output via \`/tmp/alcove-outputs.json\` 3. Exiting 0 (success) or non-zero (failure) Any executable, any language, any container. The orchestrator handles wiring. ## Implementation Order Issues are numbered 1-12 and should be implemented in sequence. Each issue references this milestone for full context.

    No due date
    •12/12 issues closed
    100% complete0 open12 closed