aidlc-portfolio
FeaturedCoordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and worktrees, validating dispatch readiness, monitoring parallel AI-DLC sessions, or synthesizing cross-project outcomes.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- awslabs
- Repository
- awslabs/cli-agent-orchestrator
- Created
- 1 years ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in `aidlc-docs/`. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for the AI-DLC method by name; also for its vocabulary — "inception phase", "construction phase", "units of work", "aidlc-docs", "aidlc-state", "workflow planning", "reverse engineer this codebase into design docs" — and when a greenfield or brownfield build should run as a governed lifecycle (requirements → stories → application design → units → per-unit design → code → build and test) instead of ad-hoc coding. Do NOT use for a single focused change, a code review, a PR, or debugging (use `pstack-skill`), for autonomous loops over Kiro specs (use `ralph-loop-kiro-specs`), or for plain subagent orchestration (use `orchestration`).
portfolio-maintenance
The run loop for an autonomous AI engineer acting as a portfolio's primary engineer — pre-flight, resume in-flight work or survey every product's live state, select the highest-value work (operate before advance), act through isolated per-run working copies and draft PRs self-promoted on genuine readiness (driving trusted-author PRs to merge), then report and bank learnings. Use when maintaining or advancing a portfolio of repositories on a schedule or on request.
portfolio-operator
Evidence-grounded cross-domain portfolio control plane for deciding what a user or small team should focus on across products, client work, research/academic commitments, growth, operations, and side projects. Use when the user asks what to do this week/next 7-30 days across multiple projects, how to allocate limited capacity, which commitments conflict, what to pause/drop/delegate, how to reconcile client deadlines with product/research work, or for a portfolio-wide review. Do not use for deep prioritization inside one product/repo, release GO/NO-GO, or executing a multi-skill workflow when a specialist/control-plane skill owns that task.