Knowns.dev
Official@knowns-dev · Vietnam
Learning, documenting, and sharing what we’ve known.
Agent Skills by Knowns.dev
Showing 10 vetted skills indexed across 1 GitHub repositories.
kn-init
Loads project docs and summarizes session-relevant context and tasks.&.#;.
kn-implement
Execute plan-driven task steps and validate acceptance criteria.
kn-research
Aggregate documentation, tasks, and code insights across repositories.
kn-plan
Convert high-level objectives into reviewable implementation plans with approval gates.
kn-spec
Create feature specification documents using Spec-Driven Development.
kn-template
Generate code from templates with dry-run validation.
kn-verify
Run SDD validation and generate coverage status reports with warnings and fixes.
kn-extract
Extract generalizable knowledge from tasks into centralized documentation.
kn-doc
Manage Knowns documentation via a unified CLI for viewing, searching, creating, and updating docs.
kn-commit
Inspect staged changes, generate conventional commit messages, and execute git commit after confirmation.
Frequently Asked Questions About Knowns.dev
FAQPage SchemaWhat specific engineering tasks does Knowns.dev enable?▼
Knowns.dev enables structured project initialization, specification-driven development, and automated knowledge extraction. It facilitates the creation of implementation plans, generates code from templates with validation, manages documentation lifecycles, and ensures commit messages adhere to conventional standards through staged change inspection.
Which personas benefit most from these capabilities?▼
Software engineers, technical leads, and documentation maintainers benefit most from these capabilities. The system is designed for developers who prioritize specification-driven development, require rigorous validation of implementation plans, and seek to maintain high-quality, searchable documentation directly within their repository environments.
What are the prerequisites for implementing Knowns.dev?▼
Implementation requires a Git-based repository environment and a local terminal interface. Users must have their project documentation structured to support the extraction and specification modules. The system relies on existing repository metadata to function, ensuring that all generated plans and documentation remain contextually relevant to the codebase.