@kobidev/apply-spec-harness
v0.3.0
Published
Apply a portable spec-driven development harness to an existing Node.js project
Maintainers
Readme
@kobidev/apply-spec-harness
Apply a portable, spec-driven development harness to an existing Node.js project.
npx @kobidev/apply-spec-harness@latest . --dry-run
npx @kobidev/apply-spec-harness@latest .
npx @kobidev/apply-spec-harness@latest . --preset servicenow-now-sdk
npx apply-spec-harness@latest . --preset servicenow-now-sdk --servicenow-release yokohama
npx apply-spec-harness@latest . --preset servicenow-now-sdk --without-tanstack-router
npx apply-spec-harness@latest . --preset servicenow-now-sdk --without-tanstack-queryIn an interactive terminal, running without --preset prompts for generic or servicenow-now-sdk. Non-interactive runs default to generic. The generic preset installs the current harness structure with starter project-specific placeholders. The ServiceNow preset prompts for the instance release and defaults to zurich. It then adds ServiceNow Now SDK rules and review skills and clones reference repositories into repos/:
- ServiceNow/ServiceNowDocs at the selected release branch into
repos/servicenow-docs - skylen15/now-sdk-mock
mainintorepos/now-sdk-mock - microsoft/playwright
mainintorepos/playwright - TanStack/router
mainintorepos/tanstack-router - TanStack/query
mainintorepos/tanstack-query
Interactive ServiceNow installs ask separately whether to include TanStack Router and TanStack Query; each defaults to yes. For non-interactive installation, use the separate --with-tanstack-router, --without-tanstack-router, --with-tanstack-query, or --without-tanstack-query options. Pass --servicenow-release to select the docs branch, otherwise it defaults to zurich. The reference repositories are cloned after installation and are not included in the npm package. Existing files and repositories are preserved unless --force is supplied; existing reference checkouts are always preserved.
