This command analyzes your project, runs a short interview with you, and creates the full agentic workflow configuration. Every step is visible on the console. When finished, the .claude/ directory, root files, manifest, and backlog are ready.
★not rated 59
changed 21d agoE✓ AI review0 tokens
originalMIT
Description: This section is filled by Bootstrap from manifest data. Required manifest fields: project.description, stack.primary, environments Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
Description: This section will be populated with data from Bootstrap's manifest files. Required manifest fields: project.description, stack.primary, project.structure Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
Not everything is worth recording. Memory stores information that will be ENCOUNTERED AGAIN later. Pass the "I would have been faster if I had known this" test: will an agent facing the same situation later benefit from this?
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
This command reads session-.json files under .claude/tracking/sessions/ and summarizes which agent is on which task, in which phase, and what it is waiting on.
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure Example output.
Read Docbase/agentic/project-manifest.yaml. Note meta.lastanalyzed and meta.codebasehash. If the manifest is missing: warn "Manifest not found. Run /bootstrap first.".
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
Purpose: Review plans created by /task-plan before /task-hunter implements them. Do not write product code. Correct plan quality, file references, acceptance checks, and scope.
★not rated 59 22d agoC0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: