mcp-server-trello: Skill for Claude Code

Dev Auto Workflow

Goal: Turn intent into a hardened, reviewable artifact, without human interaction.

CRITICAL: If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions.

HALT

To HALT with a final status and optional blocking condition:

1. Folder+id dispatch ({spec_folder} and {story_id} are set): the write-back always lands at the id-keyed story spec. The {implementation_artifacts} fallback in step 2 below is never used in this mode, even for halts before planning starts.
   • If {spec_file} is still empty, resolve it now:
     • Entry not resolved (stories.yaml is missing/unparseable, or {story_id} has no matching entry): use the fixed slug segment unresolved: {spec_file} = {spec_folder}/stories/{story_id}-unresolved.md.
     • Ambiguous on-disk match (the halt is ambiguous story file match — more than one file already matches {spec_folder}/stories/{story_id}-*.md): use the fixed slug segment ambiguous instead of deriving from the title, so the write-back neither creates a third title-derived candidate nor risks silently landing on one of the existing ambiguous files: {spec_file} = {spec_folder}/stories/{story_id}-ambiguous.md.
     • Otherwise (the entry was resolved and no ambiguous on-disk match exists): derive {spec_file} = {spec_folder}/stories/{story_id}-{slug}.md, where {slug} is a kebab-case slug from title (and description if needed) with no {story_id} prefix — the same derivation step-01's Route uses.
   • If {spec_file} exists on disk, update status in frontmatter and append missing result details under ## Auto Run Result.
   • If it does not exist, create it as a skeletal story spec:

     ---
     status: <final status>
     ---
     
     # <entry title, or "Story {story_id}" if the entry could not be resolved or the on-disk match was ambiguous>
     
     ## Auto Run Result
     
     Status: <final status>
     Blocking condition: <blocking condition, if any>
     

2. Otherwise:
   • If {spec_file} is known and exists, update status in frontmatter and append missing result details under ## Auto Run Result.
   • If {spec_file} is unknown or missing, create {implementation_artifacts}/bmad-dev-auto-result-<slug-or-timestamp>.md with:

     ---
     status: <final status>
     ---
     
     # BMad Dev Auto Result
     
     Status: <final status>
     Blocking condition: <blocking condition, if any>
     

3. Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow.on_complete
4. If the resolved workflow.on_complete is non-empty, follow it as the final instruction before exiting.
5. Stop the workflow.