菜单
Add a named project bucket to an initiative. Creates the Active Projects row, the Project section in ideas.md, the folder under the initiative root, and a 00-how-to-use.md orientation file. Use when the user wants to create a new project, add a project bucket, or group ideas under a named project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Weekly initiative health check: sync DASHBOARD.md with ideas.md, approval queue, and links; flag row vs artifact drift; verify rules/ and agents/ references; check outputs/ placement; optional one-line wiki summary on the top-tier initiative log.
Add a new initiative to the repo. Creates the initiative folder structure, registers it in DASHBOARD.md, creates ideas.md with the General project, and initializes the wiki. Use when the user wants to add a new top-level area of focus.
Mark an idea as finished, move lifecycle artifacts and outputs/ to repo archive/, update history/done-history.md with links to deliverables, tracker, and wiki. Use when the user says an idea is complete, done, shipped, or finished, or asks to close an idea successfully.
Kill an idea, record it in history/dropped-history.md, move lifecycle artifacts to repo archive/ when present, update tracker and wiki. Use when the user drops, kills, or abandons an idea, or says no-go.
Import one or more project folders from an older version of this system into a current initiative. Verifies folder structure, reconciles ideas.md, registers missing projects and ideas, repairs broken links, and updates the dashboard. Use when the user wants to bring in projects from a previous or external copy of the knowledge system.
Select the next highest priority idea from repo files, execute the next lifecycle phase for that idea, and put the result in review.
| name | add-project |
| description | Add a named project bucket to an initiative. Creates the Active Projects row, the Project section in ideas.md, the folder under the initiative root, and a 00-how-to-use.md orientation file. Use when the user wants to create a new project, add a project bucket, or group ideas under a named project. |
Use this skill when the user wants to create a named project inside an initiative. A project is a bucket that groups related ideas. All it needs to exist is a row in Active Projects, a section in ideas.md, and a folder under the initiative root.
Do not use Trello. Use only files in this repo.
Follow SYSTEM_OVERVIEW.md (project priority, naming conventions) and the target initiative's ideas.md layout.
Resolve from the user and files:
initiatives/[Initiative Name]/ folder (must exist). Ask once if ambiguous.High, Medium, or Low (or 1 / 2 / 3). Default Medium when not specified.Do not invent initiatives. Do not create a project that already exists in Active Projects for that initiative.
| Step | Action |
|---|---|
| 1 | Edit initiatives/[Initiative]/ideas.md. |
| 2 | Add a row to the ## Projects table: Project, Purpose, Priority. |
| 3 | Add a ## Project: [Exact Name] section below the existing project sections, with the standard idea table header and a placeholder row. |
| 4 | Create initiatives/[Initiative]/[Project Name]/ on disk. Add .gitkeep if no other files will be placed there immediately. |
| 5 | Create initiatives/[Initiative]/[Project Name]/00-how-to-use.md (see below). |
| 6 | If the project has an associated GitHub repo: create an empty repo/ subfolder with a .gitkeep inside. Add the Repo section to 00-how-to-use.md (see below). Do not attempt to configure the submodule — tell the user to run git submodule add <repo-url> "initiatives/[Initiative]/[Project Name]/repo" from the repo root. |
| 7 | Optionally update Last initiative work in DASHBOARD.md to today when this is a significant structural addition the user wants to count toward recency. |
The standard columns are Project, Purpose, Priority. Set Priority to the value the user specified, or default to Medium.
| [Project Name] | [Purpose one line] | Medium |
Place the new section after the last existing ## Project: section, before ## Done. Use this structure:
## Project: [Exact Name]
| Idea | Status | Priority | Last updated | Notes / next action |
|---|---|---|---|---|
| *(Add ideas here)* | | | | |
The Project column header and the section heading must match the Project column in ## Projects exactly, including spacing and casing.
00-how-to-use.mdKeep it short. Include:
[Project Name]/[Idea Name]/.ideas.md at ../ideas.md.SYSTEM_OVERVIEW.md and IDEA_LIFECYCLE.md at repo root. Adjust ../ depth by counting path segments from this file to the repo root (the file lives at initiatives/[Initiative]/[Project Name]/00-how-to-use.md, so three levels up: ../../../SYSTEM_OVERVIEW.md).Use an existing 00-how-to-use.md in the same initiative as a template when one exists. If none exists, write a minimal version using the rules above.
If the project has an associated GitHub repo, append a ## Repo section explaining that repo/ is a git submodule placeholder and providing the exact git submodule add command the user needs to run (with the correct path, leaving <repo-url> for the user to fill in).