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,089 stars 227 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 Listed

ai-portfolio-manager

Manage a whole portfolio of projects with AI — a persistent master tracker of all projects, plus weekly sprint plans that allocate tasks across AI models, subscriptions, agents, and the human, with model routing, usage-budget management, mid-sprint check-ins, remediation, and end-of-sprint cost/usage reports. Use this skill whenever the user wants to organize or track multiple projects, set up a project tracker or task list, plan their week or sprint with AI assistance, asks which AI model or tool to use for which task, mentions hitting usage limits or wanting more from their AI subscriptions, or reports being behind on a plan and needing to re-plan. Trigger even without the words "sprint" or "tracker" — phrases like "help me get all my projects under control", "I have too many things going on", "plan my AI work", "I keep running out of Claude usage", "which model should do what", or "I'm behind, what do I drop" all qualify.

1 Updated 1 months ago
aei-soli
Web & Frontend Listed

portfolio

Plan, build, critique, update, or ship a professional design portfolio as one evidence-backed system. Use when the user invokes /portfolio; needs portfolio positioning, project inventory and selection, personal brand, case studies, homepage/about/contact copy, information architecture, visual direction, website implementation, accessibility, review, or publishing; or wants to turn scattered work into a coherent portfolio for a specific role, client, or audience.

0 Updated 3 weeks ago
jpoindexter
AI & Automation Listed

portfolio-audit

Audits, renders, and bootstraps the cross-repository capability portfolio across `nolte/*` per `spec/portfolio/portfolio-management/`. Audit dispatches portfolio-manifest-collector agent for read-only inventory collection, then detects capability duplicates, surfaces gaps, verifies tech-stack consistency per `spec/portfolio/tech-stack/`, and writes a Findings-Report under `.audits/portfolio/` using Critical / Warning / Suggestion / Info severities. Render regenerates the aggregated inventory under the per-language docs/ portfolio subtree. Bootstrap creates a repository's first `project/portfolio.yml`. Invoke when the user asks to "audit the portfolio", "check for portfolio duplicates", "render the portfolio inventory", "discover the tech stack" (audit view), or equivalent German-language requests. Don't use to consolidate duplicates (operator opens cross-repo PRs), to author new capabilities, or for per-repo tech_stack capture or refresh (use tech-stack-capture). Supports resume on re-invocation.

0 Updated yesterday
nolte