Create or update Knowledge Database specifications with governance checks.
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-spec
Please help me install this Agent Skill. Skill: kb-spec Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-spec Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-spec
This Skill solves the problem of keeping the Knowledge Database consistent, complete, and governance-compliant by turning spec creation and updates into a validated, repeatable workflow.
Use cases: Drafting new requirements for an application, formalizing governance rules as specs, updating existing specs for implementation/verification stages, and ensuring every spec includes meaningful assertions for later verification.
Run the kb-spec skill with the action new and provide the SPEC-ID you want to create or update, then follow the prompted steps to validate fields, prevent duplicates, and include at least one machine-verifiable assertion.
High-intent search queries and answers about installing and using this skill.
To enforce spec-first governance rules, you must validate required fields and SPEC-NNNN ID formats before inserting new records. This prevents duplicates and ensures specification-first workflows maintain consistency across the knowledge database.
The best way to prevent duplicate specifications is to validate the SPEC-NNNN ID format and check existing records before insertion. This duplicate prevention mechanism ensures knowledge database consistency during governed spec creation.
To add machine-verifiable assertions, include at least one assertion that meets GOV-18 quality expectations when creating or updating a specification. This assertion-driven quality approach enables specs to be verified via automated checks.
Yes, you can update existing specifications during status transitions while maintaining status transition safety. The workflow enforces GOV-02 governance rules, restricting updates that would alter immutable fields or break status promotion logic.
You need to validate SPEC-NNNN ID formats whenever creating or updating specifications across lifecycle transitions. This validation is required to enforce GOV-01 spec-first workflows and prevent drift, ambiguity, and duplicate records.
A key limitation of spec-first knowledge updates is that immutable fields cannot be altered during status transitions. Governance checks restrict these updates to ensure status promotion logic remains intact and spec lifecycle integrity is preserved.
Modular-Earth-LLCDefine data requirements, schema types, and governance policies for enterprise data architectures.
masanao-ohbaValidate project deliverables against specifications and generate structured compliance reports.
ssiumhaOrganize knowledge, decisions, and TODO items with enforced naming and link patterns.
nashgaoResolve syntax, semantic, runtime, type, logic, and assertion failures in test suites.
