Initialize WikiFlow projects by creating directory structures and .wikiflow/config.json.
npx skills add https://github.com/liqunx/wikiflow --skill wf-init
Please help me install this Agent Skill. Skill: wf-init Source: https://github.com/liqunx/wikiflow/tree/main/skills/wf-init Command: npx skills add https://github.com/liqunx/wikiflow --skill wf-init
wf-init removes the setup friction of starting a WikiFlow project by creating the required wiki-driven folder structure and generating a working .wikiflow/config.json so the rest of the workflow can run.
Run /wf-init to initialize the current project with the default document directory structure and generate .wikiflow/config.json for WikiFlow.
High-intent search queries and answers about installing and using this skill.
To initialize a documentation-driven development workspace, run the setup command to generate the required wiki directory structure, bootstrap index and log files, and create a valid configuration file for subsequent workflows.
Setting up a multi-repo project with separated docs and code involves interactively confirming repository mappings, generating a central configuration file, and creating a shared wiki directory structure to link document and code repositories.
Yes, project initialization handles existing docs directories safely by preserving current content while generating missing structural folders, bootstrap wiki index files, and updating the gitignore configuration for environment files.
Yes, you can generate environment variables during project setup by using the --env option, which creates or updates your local .env file directly from an existing .env.template file.
A WikiFlow project requires a specific folder structure including docs/wiki/{current,history,deprecated,decisions}, docs/raw/00-uncategorized, and docs/changes/active directories to manage documentation lifecycle and changes.
cshyangInitialize a GSD repository structure with Git and planning documents.
liqunxMigrate OpenSpec repositories into WikiFlow docs/wiki/current and specs/spec.md formats.
token-overflowValidate code changes against design documents, environment configs, and .gitignore.
docs-plusGenerate standardized exercise directory structures with required subfolders and stub files.
