AI-DLC Portfolio

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:

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 through harness commands.
15. Advance parent work only through the persisted portfolio lifecycle.
16. Require one structured result per child and pass convergence before Learn.

Bootstrap From Work Items

The normal entry point is an operator naming a repository and one or more work items. Perform setup on their behalf:

1. Derive a stable portfolio ID from the repository and sorted work-item IDs.