analyze
Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand.
Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
Claude Code
$ npx -y skills add evidentloop/sopify --skill templates --agent claude-code
Codex
$ npx skills add evidentloop/sopify --skill templates -a codex -y
Cursor
$ npx skills add evidentloop/sopify --skill templates -a cursor -y
Gemini CLI
$ npx skills add evidentloop/sopify --skill templates -a gemini-cli -y
GitHub Copilot
$ npx skills add evidentloop/sopify --skill templates -a github-copilot -y
OpenCode
$ npx skills add evidentloop/sopify --skill templates -a opencode -y
Windsurf
$ npx skills add evidentloop/sopify --skill templates -a windsurf -y
name: templates description: Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
The Templates skill defines stable knowledge-base document structures. It does not decide when to write, how to apply `knowledge_sync`, or how a plan moves through its lifecycle.
Replace placeholders and remove empty optional sections. Do not store one-off implementation detail as long-lived knowledge.
# Project Conventions
## Technology
- Core: {language or framework version}
- Build: {build tool}
- Test: {test framework}
## Conventions
- {reusable technical convention}# Project Blueprint Index
Status: {current status}
Maintenance: keep only status, current goal, current focus, and reading links
## Current goal
- {long-term goal summary}
## Current focus
- Active plan: {none / link to plan.md}
- Archive status: {status}
## Read next
- [Project conventions](../project.md)
- [Background](./background.md)
- [Design](./design.md)
- [Tasks](./tasks.md)
- [History](../history/index.md)List each long-lived topic document in “Read next” when the `blueprint/` root contains one.
# Blueprint Background
## Long-term goals
- {goal}
## Scope
- In scope: {content}
- Out of scope: {content}
## Non-goals
- {content}# Blueprint Design
## Governing contracts
- {contract that remains valid across plans}
## Module and consumption boundaries
- {module, host, or directory responsibility}# Blueprint Tasks
## Unfinished long-term work
- [ ] {item}
## Explicit deferrals
- [-] {item and revisit condition}Keep only unfinished long-term work and explicit deferrals. Remove `[x]` items.
# Change History Index
| Date | Feature | Status | Plan package |
|------|---------|--------|--------------|
| {YYYY-MM-DD} | {feature} | {status} | [link](YYYY-MM/...) |# Long-term User Preferences
- {explicit preference that applies across tasks}{"timestamp":"{ISO-8601}","source":"chat","message":"{raw feedback}","scope":"{scope}","promote_to_preference":false}Installs into the AI coding tools you already use. Questions and small fixes are handled directly; plans start only when needed. Sopify is a set of rules and Skills that installs into the AI coding tool you already use.
Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand.
Design phase entry. Aggregates plan-level selection, task breakdown, and package output rules; loads references/assets/scripts on…
Develop phase entry; routes task execution, state updates, KB sync, and plan close-out through references/assets/scripts.
Manage long-lived `.sopify/` knowledge, including bootstrap, progressive materialization, reads, retention, and knowledge_sync…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.