Templates

All templates live in src/kiyo/templates/ and are packaged inside every Skill. They are neutral skeletons, not populated records, tools, or workflows.

Usage rules:

• Chat is the default output.
• Only the fenced artifact body is copied into a project.
• Placeholders are replaced from evidence, and unused prompts are removed.
• Populated output is never saved inside the plugin cache or product payload.
• Templates supply no default PASS, DONE, LOW risk, approval, date, count, or identity.

Init (1)

Template	Purpose
init/project-context.md	The .kiyo/policy.md locator and preferences record (see Project state)

Memory (8)

Template	Purpose
memory/index.md	Entry catalog by stable ID, plus the record envelope
memory/project.md	Purpose, boundaries, constraints, repository identity
memory/architecture.md	Observed structure versus approved intended design
memory/conventions.md	Evidenced conventions with scope and exceptions
memory/decisions.md	Proposals and traceable approved decisions
memory/domain.md	Business concepts and accepted rules
memory/integrations.md	Integration responsibilities and contracts; no secrets
memory/known-issues.md	Evidence-backed issues and unresolved drift

All Memory topic templates share the same 13-field envelope, with UNKNOWN dates and UNVERIFIED status by default.

Policies (2)

Template	Purpose
policies/organization-policy.md	Organization AI policy draft covering allowed uses, providers, data classes, tools and network, dependencies, sensitive-action approvals, prohibitions, Memory and reports, exceptions, and history. Status starts as “DRAFT — not adopted”
policies/project-policy.md	Project policy draft with parent policies, local constraints, overrides or exceptions (each with parent rule, scope, acceptance, validity), and history

Planning (3)

Template	Purpose
requirement.md	14 requirement fields plus statement origin and readiness
short-plan.md	Intent, baseline, minimal change, impact, verification, completion, replan; references the two-cycle repair bound
test-plan.md	Mode and scope, requirements, strategy and cases, environment, commands and effects, baseline, completion

Reports (16)

Most reports share the eight fields: task/scope, actions/files changed, governance/risk rationale, verification/evidence, residual issues, Memory impact, status, and next required action.

Template	Use for
compact-task-report.md	Tiny or ordinary bounded results
engineering-report.md	Material engineering work, with a requirement → implementation → check → evidence trace and self-review
approval-request.md	A missing policy-defined scoped human decision
handoff.md	Incomplete work, transfer, or a context limit
review-finding.md	One evidence-based review issue
review-report.md	Review scope, findings or zero diff, ten dimensions, limits
test-report.md	Test assessment, execution, or authoring evidence, with counts and coverage
security-assessment.md	A bounded application, Skills, or governance assessment
security-finding.md	One security finding with owner and limits
self-check-report.md	Exposed Kiyo identity, resources, and activation evidence
architecture-observation.md	The five categories: observed, approved, proposals, unknown deployment, limits
architecture-impact-report.md	A proposed change and its scoped consequences
memory-architecture-drift-report.md	Stale observations and approved-intent conflicts
memory-diff.md	A proposed entry-specific Memory delta
memory-sync-report.md	Applied, held, or no-op observation sync
memory-repair-report.md	Scoped pointer, duplicate, or structure repair

Skill governance (4)

Optional records for organizations that track Skills (KIYO-SEC-008):

Template	Purpose
skill-governance/inventory.md	Identity, source, digest, host scope, owner, approval status
skill-governance/approval.md	Approval scope, policy limits, human evidence, validity, revocation
skill-governance/revocation.md	Decision authority and proposed native response
skill-governance/incident.md	Observed versus suspected effects, data class, owner, response, closure

A revocation document is not a kill switch. Removal happens through the host.