manifest-dev
claudecodexManifest-driven workflows for inquiry, finite delivery, and optional project coordination. /figure-out investigates and reaches shared understanding, /define writes a finite Manifest with the intended Outcome, hard requirements and revisable working claims, and /do pursues the Outcome with fresh evidence while preserving source authority. Unattended execution uses host-native goal-setting when available, with a completion contract fallback. /auto chains those skills when that is the assigned work. /ticket-up preserves intent, evidence, scoped authority, and retained decisions in independently managed Tickets; /run-ticket investigates a Question or delivers Shaped work, and waits at retained acceptance before landing. /orchestrate runs a finite queue or pursues an assigned outcome within delegated authority, commissions useful work, reads designated result evidence, and records when to continue, wait, ask, or finish. Empty queues and completed implementations do not prove an outcome. Existing store and host facilities provide records and continuation; no scheduler is installed. /setup-project discovers existing direction, decisions, context, and work configuration, proposes scoped shared or private adjustments, and preserves standalone use. Product inquiry probes customer circumstances, alternatives, adoption, use, and the whole experience where relevant. Code, prompt, design, and writing reviews support the workflow. These instruction contracts and focused checks do not establish sustained project or business effectiveness.
21 skills