Thank you for your interest in contributing to directed-workflows.
Open a GitHub issue describing the problem, including:
- What you expected to happen
- What actually happened
- Steps to reproduce
- Fork the repository
- Create a feature branch from
main - Make your changes
- Submit a pull request against
main
All SKILL.md files must conform to the Agent Skills specification.
Required frontmatter fields:
| Field | Constraints |
|---|---|
name |
1-64 chars, lowercase alphanumeric + hyphens, must match parent directory name |
description |
1-1024 chars, describes what the skill does and when to use it |
Optional frontmatter fields: license, compatibility, metadata, allowed-tools.
When adding or modifying workflow examples:
- Entry points are always
SKILL.mdwith valid YAML frontmatter per the spec above - Phase files live under
references/and usephase-0N-name.mdnaming - The
parentfield references the router's name, not its filename - Follow the Inspect-Decide-Generate cycle in every step
- Use Status-Action tables for conditional logic, not prose
- Create a directory under
examples/<domain>/<workflow-name>/ - Add a
SKILL.mdrouter as the entry point - Add phase files under
references/ - Update the examples table in
README.md
- Place new templates under
templates/ - Single-session workflows: one
.mdfile - Multi-session workflows: a directory with
router.mdandphase-template.md
Be respectful. Constructive feedback is welcome; personal attacks are not.
Every PR must:
- Not break existing workflow file structure
- Follow the naming conventions documented in
ROUTER_PATTERN.md - Conform to the Agent Skills specification — all
SKILL.mdfiles must have valid frontmatter with requirednameanddescriptionfields - Include a clear description of what the change does and why
There is no build step. Review your markdown renders correctly and all internal @-references resolve to existing files.
By contributing, you agree that your contributions will be licensed under the GNU General Public License v3.0.