Skip to content

Add blueprint skill for template-based DAG authoring#150

Open
tayloramurphy wants to merge 6 commits intomainfrom
tayloramurphy/blueprint-skill
Open

Add blueprint skill for template-based DAG authoring#150
tayloramurphy wants to merge 6 commits intomainfrom
tayloramurphy/blueprint-skill

Conversation

@tayloramurphy
Copy link
Contributor

Summary

  • Adds new blueprint skill for working with the airflow-blueprint package
  • Enables platform teams to define reusable Airflow task group templates with Pydantic validation
  • Supports composing DAGs from YAML without writing Airflow code

References

Test plan

  • Verify skill loads correctly with claude plugin install
  • Test skill triggers on relevant user queries
  • Validate CLI commands work as documented

Blueprint enables platform teams to define reusable Airflow task group
templates with Pydantic validation, allowing non-engineers to compose
production DAGs from YAML without writing Airflow code.
Add implementation workflow diagram, prerequisites, validation checklist,
troubleshooting section, and user testing requirements to match the
structured approach used in cosmos-dbt-core and cosmos-dbt-fusion skills.
Change from human documentation style to agent instruction style:
- Open with role-setting ("You are helping a user...")
- Add decision table for routing user requests
- Use imperative language throughout
- Remove explanatory prose, focus on actionable guidance
- Add verification checklist as agent action
Ensure open source Blueprint usage is the default focus, with Astro IDE
integration clearly marked as "Astro Customers Only" sections.
Copy link

@yetudada yetudada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left minor comments, I think I'm okay with the IDE content remaining here.


### Astro Customers Only

Skip this section unless the user is an Astro customer using the Astro IDE.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’m not sure how best to phrase this, but my Claude setup currently does this automatically every time I create or modify a Blueprint.

Would it be possible for the agent to detect, or ask, whether the project is an Astro project, and then handle this automatically for users?

Copy link
Contributor Author

@tayloramurphy tayloramurphy Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to check for a .astro directory and/or ask the user if they'r an astro customer. @igorastronomer what do you think of this approach?

And would appreciate a deeper review of the skill since we'll want it in the IDE.

…projects

- Update minimum version to Blueprint 0.11.0+ (required per reviewer)
- Auto-detect Astro projects and regenerate schemas automatically
  when blueprints are created or modified, instead of requiring manual
  steps behind an "Astro Customers Only" gate
@tayloramurphy tayloramurphy self-assigned this Mar 5, 2026
@tayloramurphy tayloramurphy marked this pull request as ready for review March 6, 2026 15:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants