Skip to content

Improve .preflight/ example configs with clearer comments and practical defaults - #34

Closed
TerminalGravity wants to merge 4 commits into
mainfrom
improve-preflight-example-configs
Closed

Improve .preflight/ example configs with clearer comments and practical defaults#34
TerminalGravity wants to merge 4 commits into
mainfrom
improve-preflight-example-configs

Conversation

@TerminalGravity

Copy link
Copy Markdown
Collaborator

Rewrites the example .preflight/ config files to be more user-friendly:

  • Relative paths instead of absolute in related_projects examples (more realistic)
  • More domain examples in always_check (billing, auth) and skip (git status, npm test)
  • Clearer profile descriptions explaining what each level actually does for your prompts
  • Better README with env var fallback table and guidance to commit configs to version control
  • Practical triage.yml with commented-out examples for easy customization

No code changes — documentation/examples only.

… and contracts

The README references .preflight/ config extensively but there were no
concrete example files to copy. This adds a ready-to-use examples/.preflight/
directory with annotated config.yml, triage.yml, and contracts/api.yml,
plus a README explaining how to use them.
Created examples/USAGE_EXAMPLES.md with 8 real-world scenarios showing
what each tool looks like in practice: preflight_check catching vague
prompts, scope_work creating execution plans, enrich_agent_task for
sub-agents, sharpen_followup resolving ambiguity, session health checks,
semantic history search, weekly scorecards, and prompt grading.

Added link to usage examples in README nav bar.
…al defaults

- Use relative paths instead of absolute in related_projects examples
- Add more domain-specific always_check examples (billing, auth)
- Clearer profile descriptions explaining what each level actually does
- Better README with env var fallback table and commit-to-vcs guidance
- Add practical skip examples (git status, npm test, type-check)
The README references examples/.preflight/ but the files didn't exist.
Added config.yml, triage.yml, and README.md with all options documented
and sensible defaults shown.

@TerminalGravity TerminalGravity left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

The example configs are well-annotated — exactly the kind of thing that saves new users 30 minutes of guessing. The contracts example with the User interface is practical without being toy-ish.

One note: PRs #33 and #29 also include these same example config files (looks like they were cherry-picked or rebased together). Might want to land this one as the canonical source and strip the duplicates from the others to avoid merge noise.

LGTM otherwise.

@TerminalGravity

Copy link
Copy Markdown
Collaborator Author

Superseded by newer PRs.

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.

1 participant