Skip to content

Kartik-Doye/Ravengard-AI-Recruiter / agent/skills/distill

distill

Verified

Turns a vague software request into a compact implementation brief with actors, triggers, preconditions, behavior, failures, permissions, data effects, edge cases, and observable acceptance conditions. Use before planning when product intent or scope is ambiguous.

FileKindSize
SKILL.mdskill md10.0 KB
references/brief-template.mdmarkdown3.4 KB
references/research.mdmarkdown832 B

references/brief-template.md

View on GitHub
# Brief template + worked example

## Template

```markdown
<!-- generated by distill on YYYY-MM-DD -->
# Brief: <title>

## Goal
<One sentence: what becomes true, for whom.>

## User outcome
<What the user experiences differently. One or two sentences.>

## Context
- <Existing piece the work touches: path + one line.>
- <Command/environment facts that constrain the work.>

## Constraints & conventions
- <Project conventions discovered in the repo that must be respected.>

## Scope
- <In: concrete deliverables.>

## Non-goals
- <Out: explicitly not doing, tempting as it is.>

## Agent-executable specifications
- [ ] <Unambiguous, checkable statement a downstream agent can verify without human judgment.>
- [ ] <Example: "Toggling the theme writes 'dark' or 'light' to localStorage", not "Theme looks good.">

## Edge cases
- <Empty/error/loading/malformed states worth handling.>

## Non-functional requirements
<Only when they bite: performance budget, accessibility bar, i18n,
security constraint. Omit the section if nothing exceeds the project's
existing bar.>

## Compatibility & migration
<Only when existing data/users are affected: what stays backward
compatible, what migrates, what breaks.>

## UX expectations
<Only for user-facing work: behavior expectations, not visual design.>

## Verification
- <Command that must pass, e.g. `npm test`.>
- <Human/browser check, e.g. "user can toggle theme and it survives reload.">

## Known unknowns & assumptions
- A1: <falsifiable assumption made instead of asking.>
- U1: <open question, non-blocking.>

## Suggestions (non-binding)
- <At most 3, clearly optional.>
```

## Worked example (abridged)

Input: "bro add dark mode make it good"

```markdown
# Brief: dark mode toggle for the dashboard

## Goal
Users can switch the dashboard between light and dark themes, and the
choice persists across sessions.

## User outcome
Comfortable viewing in low light; the app remembers the preference.

## Context
- Tailwind configured with CSS variables: `tailwind.config.ts`
- Theme not stored anywhere today; no user preferences table exists.

## Constraints & conventions
- Colors must come from existing CSS variables (no hardcoded hex).
- Follow existing toggle component pattern in `src/components/Toggle.tsx`.

## Scope
- Theme toggle in the settings page + header
- Persisted preference (localStorage; no account-level sync)
- Default follows `prefers-color-scheme`

## Non-goals
- Per-user server-side theme storage
- Theming beyond the two modes

## Agent-executable specifications
- [ ] Toggling switches theme with no full page reload
- [ ] Preference survives page reload and is readable from localStorage
- [ ] First visit matches OS preference (prefers-color-scheme)
- [ ] No flash of wrong theme on load (blocking script injection if SSR)

## Edge cases
- OS preference changes while app is open (only applied on next visit)
- `localStorage` unavailable (falls back to OS preference)

## Verification
- `npm run build` and `npm test` pass
- Manual: toggle → reload → verify persistence in both directions

## Known unknowns & assumptions
- A1: localStorage is acceptable persistence (no auth system exists).
- U1: should the auth page (future) also respect the theme?

## Suggestions (non-binding)
- Consider `next-themes` if hydration flash proves annoying.
```

Note what the example *doesn't* contain: no Tailwind tutorial, no design
philosophy, no invented requirements. That's the target density.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall