aid-design-job
Develop a scheduled or background job design as a DESIGN SEED in `.aid/design/job.md` -- the trigger, the work it performs, and its idempotency and failure handling. Use this skill when a job's schedu
Файлы1
Открыть в GitHubSKILL.md.claude/skills/aid-design-job/SKILL.md
GitHubDesign Job (develop a design seed, resolve nothing)
Bind VERB=design, ARTIFACT=job -- the design stage in the contract's
vocabulary -- then follow the shared contract at
.aid/runtime/templates/design-lifecycle.md. This skill binds that contract and
restates none of its rules. The seed it writes is .aid/design/job.md; realizing it into
the built job is /aid-create-job's job, not this one's.
- Boundary vs
/aid-create-job: that skill builds the job from a ready seed; this one only develops the seed. Neither resolves anything on its own -- the user decides when a seed is ready to realize. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose}
entry line on each state.
State: INTAKE
- Require a subject. Empty argument -> ask one bootstrapping question ("What job do you want to design -- its trigger, the work it performs, and its failure handling?") and wait.
- Allocate through the Work Initiation Gate exactly as the contract's Allocation rule
requires (
.agents/skills/aid-design/SKILL.mdINTAKE step 4 is the shape), withinitiator: aid-design-job.phaseis not driven. - Acquire
.aid/design/per the contract, then read.aid/design/job.mdif a prior seed exists -- re-invocation iterates it rather than starting over. - Classify complexity for the
aid-architectdispatch (verifier tier >= producer).
Advance: DESIGN.
State: DESIGN
Dispatch aid-architect (clean context, tiered) to write or iterate
.aid/design/job.md in the seed shape the contract fixes (design-seed.md;
feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read
in INTAKE. What this artifact's seed must settle: the trigger, the work it performs, and
its idempotency and failure handling; its ## Destination names where the built job
lands. Never writes .aid/knowledge/ and never writes production code -- the design
invariant (design-lifecycle.md).
Advance: VERIFY.
State: VERIFY
Full verify, as design-lifecycle.md defines it. Not clean -> loop to DESIGN; the
3-cycle circuit breaker there escalates to IMPEDIMENT + lifecycle: Blocked.
Advance: PRESENT.
State: PRESENT (hard stop -- the user decides)
Set lifecycle: Paused-Awaiting-Input. Present the seed clearly. Assert no resolution --
the user iterates (re-invoke this skill) or realizes it now (/aid-create-job).
Advance: DONE.
State: DONE
Set lifecycle: Completed, updated now, append a ## Lifecycle History row. The seed
persists at .aid/design/job.md; consumption happens at /aid-create-job.