Record project history and decision rationale in structured documentation.
npx skills add https://github.com/projectmiluju/factlog --skill docs-projectmiluju
Please help me install this Agent Skill. Skill: docs Source: https://github.com/projectmiluju/factlog/tree/main/.agents/skills/docs Command: npx skills add https://github.com/projectmiluju/factlog --skill docs-projectmiluju
This skill acts as the dedicated historian for a project, ensuring every decision, context, and outcome is captured in a traceable, non-ambiguous format. It prevents loss of knowledge by requiring structured documentation rather than ad-hoc notes.
Create a Dev Log entry under docs/devlog with today's date and a descriptive title to begin recording history.
High-intent search queries and answers about installing and using this skill.
Architecture decision records capture technical choices, rationale, and alternative considerations to maintain traceability. You record context, decisions, and trade-offs in structured ADRs to ensure accountability and prevent knowledge loss across the project lifecycle.
Development logs provide traceability by recording context, decisions, and outcomes in a consistent format. Using standardized templates under a dedicated devlog directory ensures project history is captured non-ambiguously rather than through ad-hoc notes.
Documenting project history involves applying consistent templates across dev logs, ADRs, README updates, and STATUS.md files. This structured approach captures why choices were made, alternatives considered, and lessons learned to enforce accountability.
Mandatory frontmatter in SKILL.md enforces consistent documentation by requiring structured metadata. This ensures every decision, context, and outcome is captured in a traceable format, preventing the loss of knowledge from unstructured or ad-hoc notes.
Structured templates support project status updates by keeping STATUS.md and README files current with changes and rationale. This ensures the project status remains up-to-date for audits and onboarding by consistently documenting context and decisions.
Ad-hoc documentation fails to capture decision rationale because it lacks structured templates and mandatory frontmatter. Without enforcing consistent formats for context, decisions, and trade-offs, project history becomes ambiguous and knowledge is easily lost.
fukukei23Record project decisions and session outcomes into structured markdown documentation.
Ronin15Generate a structured Markdown changelog from SDL3 HammerEngine git history.
louloulinValidate SKILL.md files for YAML frontmatter, required fields, and content.
rijnbStandardize per-note wiki ingestion with conversion, classification, and logging workflows.
