← FievelCONTENT HISTORY

Update to Fievel

Snapshot Nov 6, 2026 · 00:15 UTC · version 0.3.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Fievel and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build or improve portable Fievel content standards and product context using user decisions and approved sources.",
  "included_files": [],
  "name": "content-system-builder",
  "skill_md_contents": "---\nname: content-system-builder\ndescription: Build or improve portable Fievel content standards and product context using user decisions and approved sources.\n---\n\n# Content System Builder\n\n## Using this skill from the Fievel plugin\n\nThis plugin carries Fievel's workflows and Python tools. The user's project is\nseparate from the installed plugin. Find the plugin root two directories above\nthis SKILL.md; its `runtime/` directory is the bundled resource root, called R below.\nResolve R from this skill's actual installed path, never a development checkout.\n\n- Prefer Fievel's MCP tools when they are available (names start with `fievel_`).\n  Local tools such as `fievel_init`, `fievel_validate`, `fievel_check` and\n  `fievel_view` work only inside the user's workspace and never overwrite files;\n  call `fievel_setup_status` first. Remote tools such as `fievel_validate_package`\n  and `fievel_check_responses` receive package content, store nothing, and return\n  results to save as new files; tell the user that content is sent to the Fievel\n  server for processing. Without tools, use the CLI as described below.\n- Read `R/AGENTS.md` for Fievel's conversation and workflow rules. References in\n  this skill and in AGENTS.md to AGENTS.md, docs/, knowledge/, templates/, examples/,\n  schemas/, scripts/ and .agents/skills/ are relative to R, not the user's working directory.\n- Keep the current working directory in the user's chosen workspace. Run the CLI\n  by its absolute path: `python \"R/scripts/fievel.py\" <command> <project> ...`.\n  Replace R with the resolved path. Resolve project and output paths in the user's\n  workspace. Run one simple command per step: the Python interpreter\n  with the CLI path and its arguments, without chained commands, shell variables\n  or PowerShell scripts. Read and list files with the host's file tools. Simple\n  commands keep the user's permission prompts clear and predictable. Never create\n  projects, install dependencies, or edit inside R or the plugin cache. Never copy Fievel AGENTS.md over a user's repository instructions.\n- Check Python 3.10+ and `python -c \"import jsonschema\"`. If missing, explain the\n  prerequisite. When setup is authorized, create a new `.fievel-venv` in the user's\n  workspace and install `R/requirements.txt` with its Python. Reuse a working\n  environment; do not overwrite an existing environment. Use that interpreter for\n  every CLI command. Do not install globally or claim the plugin bundles Python.\n- Follow existing workspace instructions. Explain that project files remain local,\n  but material read into the conversation is handled by the user's coding agent.\n- The repository-maintenance and adapter-sync instructions in R/AGENTS.md are for\n  Fievel development, not for modifying the installed plugin during a user session.\n- Other Fievel skills in this plugin: getting-started, content-system-builder,\n  source-discovery, ai-behavior-designer, evaluation-designer and content-audit.\n  Switch to the one that fits when the user's request changes.\n\nSave projects under the user's chosen folder (default `my-content-system/` in\ntheir workspace). The user approves content; validation does not. Do not run\nmodel evaluations unless the user authorized them.\n\n## Workflow\n\nRead AGENTS.md, docs/WORKFLOW.md and the selected project's progress.json.\nRequired inputs: selected project folder, product/audience intent, and any supplied\nstandards. Start with stages 1 and 2; ask only for missing decisions. When the\nuser supplies or names a source document, run the source-discovery skill first to\ninventory and assess it; then use the existing-guidelines path to map its rules,\npreserving their source IDs and approval status. Do not turn inferred preferences into approved organization rules.\n\nFor existing material, read knowledge/content-design/using-existing-guidelines.md.\nShow a small source-to-proposed-rule mapping with precise evidence location where\navailable. Preserve meaning and distinguish explicit requirements from examples or\ninterpretation. Where the schema lacks a locator, keep a scoped review note rather\nthan invent fields or call a source ID verified evidence. Missing policy stays unknown.\n\nRead knowledge/content-design/content-systems.md for beginner explanations only.\nCreate product.json and standards.json using templates/content-system as the shape.\nUse stable rule IDs. Draft recommendations have status draft and empty source_ids\nunless grounded in a recorded source. Collect accessibility/localization needs;\nleave unknowns in progress.open_questions. Introduce a reusable language pattern\nwith an example. Continue through sources, behavior, quality, and governance via\ndocs/WORKFLOW.md; this skill can coordinate the complete seven-stage workflow.\n\nOutput: changed package files, saved decisions and next_action. Run\n`python scripts/fievel.py validate <folder>` to check structure/links and show\nuncovered draft rules. Do not force stage-5 checks into earlier stages merely to\nmake a draft valid. At stage 5, give every rule a linked scenario/check, then run\n`python scripts/fievel.py validate <folder> --require-coverage` before execution.\nStructural validity and coverage are not content approval or completion.\nWhen useful, generate a read-only overview with\n`python scripts/fievel.py view <folder> --out <new.html>` and explain the changed\nrule's declared source/check connections. Regenerate to a new file after edits;\nthe prior snapshot does not update itself. Missing evidence remains a visible gap.\nSummarize significant changes before editing; request approval before overwriting\nuser-owned assets outside the agreed editing scope. On validation failure, explain\nthe specific file/link and repair only the agreed project.\nExample: “Use calm language” -> draft rule -> human tone-review question.\n"
}

SHA-256 of public snapshot: b78342fa61ab7b9730e570d7f32e290b597e636a1f019a29646b012148b92baf