SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillstk-to-spec

tk-to-spec

Writing & research

View repository

Updated 10-15 21:03

About this skill

Evidence를 specconvert to

explicitly /tk-to-spec or $tk-to-spec Execute only when is selected. Input is source evidence that can actually be read, such as conversations, issues, artifacts, and repository investigation results. Do not call other skills or modify implementation, tickets, or remote state.

Output contract

Only when there is valid source evidence, write to the current repository root's .tigerkit/spec.md, and first git rev-parse --show-toplevelconfirm the root with, then report in the result the actual absolute path derived from that root. The document must be self-contained Markdown that directly includes the following.

  • Status: Pending (not consumed by downstream until the user explicitly approves)
  • source/R-AC and lineage (the connection between each claim and its source)
  • goal, scope, exclusions, constraints
  • acceptance criteria and verification commands/evidence
  • mark facts, confirmed decisions, and unverified claims separately
  • missing evidence and conflicts and their impact
  • Write explanatory sentences and headings in Korean, and keep only exact fields, statuses, IDs, commands, paths, URLs, and literals in their original form.

Procedure

  1. Read the source and classify each sentence as Fact | Confirmed decision | Unverified claim.
  2. Do not fill in missing information; write it as Missing evidence. For contradictions, write both sides' evidence and the resolution owner as Conflict, and set the status to Blocked or Unverifiable.
  3. Write goal/scope/exclusions/constraints/acceptance/verification/lineage. Also keep technical literals, changed paths, and failure conditions exactly as in the original.
  4. Before saving, check whether it is self-contained and whether there is an approval boundary. If the user approves, that explicit approval alone can change it to Pending을 Ready.

Even if information is insufficient, create a self-contained document, specify the missing items and absolute paths, and then Status: Unverifiablestop at. If a conflict is not resolved, preserve both sides' evidence and Status: Blockedstop at. .tigerkit/ Do not create any state other than, archive/current pointer/global settings.

Boundary

Do not trigger for general planning, implementation, ticket decomposition, or simple questions. Do not promote facts to inferences, and do not pass Pending documents as downstream input.