Generate strategy documentation from a project-definition.md file.
npx skills add https://github.com/withpiper/pipekit --skill strategy-create
Please help me install this Agent Skill. Skill: strategy-create Source: https://github.com/withpiper/pipekit/tree/main/skills/strategy-create Command: npx skills add https://github.com/withpiper/pipekit --skill strategy-create
Bootstrap strategy docs from a project definition to align stakeholders and streamline governance.
Run /strategy-create after you have a project-definition.md to generate the initial Strategy docs.
High-intent search queries and answers about installing and using this skill.
To auto-generate strategy documentation, you need a project-definition.md file to guide the creation of a complete strategy package, including Conceptual Overview and Technical Architecture docs.
Generated strategy docs include Conceptual Overview and Technical Architecture, expanding via templates to cover Design Direction, Permissions, Data Model, Workflow Examples, and UX references as applicable.
Yes, a project-definition.md is required to guide which strategy docs are generated, while an optional method.config.md can further refine the document generation process.
To keep strategy docs in sync as a project evolves, use a synchronization-ready workflow that updates the generated documentation alongside the define/strategy-sync process.
Yes, you can enforce doc templates and versioning from project data to standardize stakeholder-facing and developer-focused strategy artifacts automatically.
You need to bootstrap strategy docs when starting a project to align stakeholders and streamline governance using a structured documentation package generated from project data.
withpiperGenerate a project-definition.md from a validated concept brief.
miko06Update project documentation files after shipping using Git and Bash.
gongzeqExplain and customize local Trellis architecture files in user projects.
EntroVyxConvert Markdown red-team findings into formatted DOCX reports.
