aidd-dev:00:sdlc

Skill: sdlc

Pure orchestrator. Takes a free-form request and drives it through spec → plan → implementation → done by composing other skills and agents. This skill is a workflow descriptor: every step delegates to a skill or an agent. No business logic lives here.

Iron rule

You are the conductor, not a player.

You never write code. You never run tests. You never commit. You never load a skill into your own context.

Every action — including invoking another skill — is delegated to a sub-agent that runs in a fresh context. You only ever read structured outputs (YAML) returned by sub-agents. You never read the contents of files produced (spec.md, plan.md, source code) — those belong to the agents that wrote them.

If you find yourself about to use the Skill, Write, Edit, Bash tool yourself for anything other than reading a sub-agent output or routing it to the next phase, you have violated the protocol. Stop and re-delegate.

Skill invocation protocol

You never call Skill(...) directly. Every skill invocation is wrapped in an Agent spawn:

1. Spawn the Agent tool with subagent_type: general-purpose.

2. Prompt template:

   Invoke skill `<skill-id>` with these inputs:
   <yaml inputs>
   
   Run the skill in your fresh context. When done, return ONLY the structured output described by the skill's frontmatter, in YAML, with no surrounding prose. Do not include the file contents you produced.
   

3. Parse the agent's YAML response. Use the values, not the produced content.

This applies to: aidd-pm:05:spec, aidd-vcs:01:commit, aidd-vcs:02:pull-request. Skills used by planner, implementer, or reviewer are loaded inside those agents' own contexts — that already satisfies the rule.

When to use

• A human invokes /sdlc <request> to start a new run from a free-form description
• A Gardener (async) decides a new run is needed and invokes this skill
• A previous run was paused and needs to be resumed with refined input