setup-ftr
Initialize for-the-record in .things/ - creates docs directory, registers collection, writes preferences. Required before /add-doc-ftr can store documents.
What this skill does
<purpose>
Initialize the `for-the-record` plugin within `~/.things/`. Creates the docs directory, registers the collection in the registry, writes preferences, and sets up empty index files.
</purpose>
<steps>
<step id="load-config" number="1">
<description>Load Configuration</description>
<load-config>
<action>Resolve the user's home directory.</action>
<command language="bash" output="home" tool="Bash">echo $HOME</command>
<constraint>Never pass `~` to the Read tool.</constraint>
<read path="<home>/.things/config.json" output="config" />
<if condition="config-missing">Tell the user: "Run `/things:setup-things` first to initialize .things/." Then stop.<exit /></if>
<if condition="reconfigure-argument">
<read path="<home>/.things/for-the-record/preferences.json" output="existing-prefs" />
<action>Show current settings as defaults throughout.</action>
</if>
</load-config>
</step>
<step id="create-directories" number="2">
<description>Create Plugin Directories</description>
```bash
mkdir -p <home>/.things/for-the-record/docs
mkdir -p <home>/.things/for-the-record/discussions
```
</step>
<step id="gather-preferences" number="3">
<description>Gather Preferences</description>
<ask-user-question>
<question>What level of detail should documents capture by default?</question>
<option label="Concise (Recommended)">Key points, decisions, and outcomes — compact and scannable</option>
<option label="Detailed">Full reasoning chains, code blocks, all alternatives discussed — maximum context preservation</option>
</ask-user-question>
<ask-user-question>
<question>Should documents auto-generate tags from content?</question>
<option label="Yes (Recommended)">Automatically suggest tags from technologies, keywords, and existing tag vocabulary</option>
<option label="No">I'll add tags manually each time</option>
</ask-user-question>
<ask-user-question>
<question>Should verbatim discussions be automatically pruned after a number of days?</question>
<option label="No retention limit (Recommended)">Keep all discussions indefinitely</option>
<option label="30 days">Auto-prune discussions older than 30 days</option>
<option label="90 days">Auto-prune discussions older than 90 days</option>
<option-with-text-input>Custom number of days</option-with-text-input>
</ask-user-question>
</step>
<step id="write-preferences" number="4">
<description>Write Preferences</description>
<write path="<home>/.things/for-the-record/preferences.json">
```json
{
"default_detail_level": "<concise|detailed>",
"auto_tag": <true|false>,
"discussion_retention_days": <number or null>
}
```
</write>
</step>
<step id="write-index-files" number="5">
<description>Write Empty Index Files</description>
<if condition="index.json missing">
<write path="<home>/.things/for-the-record/index.json">
```json
{
"version": 1,
"last_updated": "<current_date>",
"total_items": 0,
"items": []
}
```
</write>
</if>
<if condition="tags.json missing">
<write path="<home>/.things/for-the-record/tags.json">
```json
{
"last_updated": "<current_date>",
"tags": {}
}
```
</write>
</if>
</step>
<step id="register-collection" number="6">
<description>Register Collection in Registry</description>
<read path="<home>/.things/registry.json" output="registry" />
<action>Add (or update) the `for-the-record/docs` and `for-the-record/discussions` collection entries.</action>
<schema name="collection-entry">
```json
{
"for-the-record/docs": {
"plugin": "for-the-record",
"description": "Structured documentation captured from conversations and context",
"tags_field": "frontmatter.tags",
"item_structure": {
"directory_per_item": false,
"file_pattern": "*.md"
},
"index_schema": {
"required_fields": {
"filename": "string",
"title": "string",
"date": "date",
"tags": "string[]"
},
"optional_fields": {
"description": "string",
"detail_level": "string",
"source_type": "string"
}
},
"master_index": "for-the-record/index.json",
"rebuild_command": "python3 ${PLUGIN_PATH:for-the-record@brenna-plugs}/scripts/rebuild-index.py ${THINGS_PATH}"
}
}
```
</schema>
<schema name="discussions-collection">
```json
{
"for-the-record/discussions": {
"plugin": "for-the-record",
"description": "Verbatim conversation captures preserved without summarization",
"tags_field": "frontmatter.tags",
"item_structure": {
"directory_per_item": false,
"file_pattern": "*.md"
},
"index_schema": {
"required_fields": {
"filename": "string",
"title": "string",
"date": "date",
"tags": "string[]"
},
"optional_fields": {
"description": "string",
"source_type": "string"
}
},
"master_index": "for-the-record/index.json",
"rebuild_command": "python3 ${PLUGIN_PATH:for-the-record@brenna-plugs}/scripts/rebuild-index.py ${THINGS_PATH}"
}
}
```
</schema>
<action>Merge both into `registry.json`'s `collections` object and write the file.</action>
</step>
<step id="update-environment" number="7">
<description>Update Environment Tracking</description>
<action>Read `config.json`, find the current hostname's environment entry, and add `"for-the-record"` to its `plugins` array if not already present. Write back.</action>
</step>
<step id="git-workflow" number="8">
<description>Handle Git Workflow</description>
<git-workflow>
<action>Read git workflow from `config.json` (`git.workflow`).</action>
<if condition="workflow-auto">Automatically `git add`, `git commit -m "setup: for-the-record"`, and `git push`.</if>
<if condition="workflow-ask">
<ask-user-question>
<question>Commit and push the for-the-record setup?</question>
<option>Yes -- commit and push</option>
<option>Commit only</option>
<option>No -- I'll handle git myself</option>
</ask-user-question>
</if>
<if condition="workflow-manual">Tell the user the setup is complete and they can commit when ready.</if>
</git-workflow>
</step>
<step id="confirm" number="9">
<description>Confirm Setup</description>
<completion-message>
for-the-record is ready!
- Docs directory: `<home>/.things/for-the-record/docs/`
- Discussions directory: `<home>/.things/for-the-record/discussions/`
- Detail level: `<default_detail_level>`
- Auto-tagging: `<auto_tag>`
- Discussion retention: `<discussion_retention_days or "unlimited">`
- Collections registered: `for-the-record/docs`, `for-the-record/discussions`
Start capturing:
- `/add-doc-ftr <topic>` -- Capture a document from conversation context
- `/add-doc-ftr <topic> --detailed` -- Capture with maximum detail
- `/capture-discussion` -- Capture a verbatim discussion (no summarization)
- `/import-ftr <path>` -- Import existing documentation files from any directory
</completion-message>
</step>
</steps>
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.