Abhishekmishra2808 commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4028872803
My intention was not to introduce a separate documentation layer that needs to be maintained independently from the contributing guide. The contributing documentation would still remain the canonical source of truth for the workflow description. What I had in mind is closer to treating certain parts of the documentation as structured workflow sections, where the actionable parts of the workflow (commands, fallbacks, environment transitions) are written in a consistent format that a generator can extract. In other words, the structure would live directly inside the documentation rather than in a separate YAML file that must be maintained alongside it. The generator would simply scan the documentation for those structured sections, build an internal workflow model, and generate the corresponding agent skill definitions from it. This way the docs remain both the human-readable explanation and the authoritative workflow description, while the generation step ensures agents get a deterministic structure to follow. Conceptually the flow would look something like: Contributing Docs -> Structured Workflow Sections ->Workflow Extraction Script -> Internal Workflow Model ->Agent Skills This keeps the documentation as the single place contributors edit, avoids maintaining a separate workflow spec, and still provides a structured representation that can be validated and transformed into agent skills. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
