aidlc-portfolio

Featured

Coordinate 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.

AI & Automation 1,350 stars 277 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 89/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# AI-DLC Portfolio Maintain a thin control plane around existing AI-DLC workflows. Never replace or modify the child workflow engine. Resolve every relative resource path against the directory containing this `SKILL.md`. In the commands below, set `SKILL_DIR` to that absolute directory: ```bash SKILL_DIR=/absolute/path/to/skills/aidlc-portfolio ``` ## Operating Rules 1. Run `"$SKILL_DIR/scripts/portfolio.ts"` for every portfolio mutation. 2. Keep portfolio state at `<root>/portfolio` and project checkouts at `<root>/repositories`. 3. Give each active child intent its own path under `<root>/worktrees`. 4. Dispatch one `aidlc_runner` per child intent with CAO `assign`. 5. Treat child AI-DLC state as opaque. Never edit `aidlc-state.md` or derive its next stage. 6. Require evidence and confidence for discovered catalog relationships. 7. Ask the human about missing or uncertain business facts before verification. 8. Run dispatch validation before starting or resuming a child runner. 9. Treat the portfolio supervisor as the sole shared-memory approval authority. 10. Never merge worktree-local `project.md` or `team.md` changes. 11. The supervisor owns bootstrap; the operator should not have to prepare the workspace, repository checkout, intent files, worktrees, or child harness. 12. Never dispatch until portfolio discovery has explicit human confirmation. 13. Never answer a child AI-DLC question without human input. 14. Stage, project, and verify child harnesses only ...

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

AI & Automation Featured

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`).

96 Updated 4 days ago
fabricioctelles
AI & Automation Listed

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.

3 Updated today
devantler-tech
AI & Automation Listed

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.

1 Updated today
CometWeb-io