cody-product-builder

Name: cody-product-builder
Author: ibuildwith-ai

65stars9forks

How to install cody-product-builder?

ibuildwith-ai/cody-product-builder/cody-product-builder

$npx -y skills add ibuildwith-ai/cody-product-builder --skill cody-product-builder

Installs into the current project.

Summary

Guides knowledge workers and domain experts from idea to finished product through a structured two-phase workflow (Plan and Build). Use this skill whenever the user wants to plan, design, build, or ship a product, app, tool, or feature; add a new version or patch to an existing p

Files · 1

View on GitHub

SKILL.md

1	# Cody Product Builder
2
3	## Agent Instructions
4	- Read this entire document (`SKILL.md`) and commit it to memory.
5	- Make sure you check this document often if you need to understand how to process any Cody Product Builder commands.
6	- Anything that has [AGENT TODO: to do item] means you need to take action.
7	- When you see AGENT ANNOUNCE, anything in between the ```[message]``` (tick marks), you will display to the user exactly as stated.
8	- After every phase, make sure you re-read this document.
9	- {{cfPlaceholders}} used in commands are defined in this document, under the "Template Placeholder Values" section. When you see a placeholder, you will replace it with its appropriate value.
10	- The roles are as follows:
11	- USER Is the human guiding you in the building process.
12	- AGENT That's you! The AI Development AGENT.
13	- For detailed phase descriptions, document references, and version naming conventions, see `{{cfReferences}}/phases.md`.
14
15	## Template Placeholder Values
16	These placeholders are a pointer to actual values. They are created here and used throughout various commands. When you encounter a placeholder, you will replace it with its value and consider that as the literal (e.g. `{{cfCommands}}/help.md` translates to `commands/help.md`).
17
18	The skill-file placeholders (`{{cfRoot}}`, `{{cfAssets}}`, `{{cfCommands}}`, `{{cfReferences}}`) are paths relative to this skill's own folder.
19
20	\| Placeholder \| Maps to \| Description \|
21	\|------------\|---------\|-------------\|
22	\| {{cfRoot}} \| . \| This skill's root folder. \|
23	\| {{cfAssets}} \| assets \| Cody assets folder (templates and other static resources). \|
24	\| {{cfCommands}} \| commands \| Cody commands to be executed. \|
25	\| {{cfReferences}} \| references \| Shared reference content loaded on demand by commands. \|
26	\| {{cfProject}} \| Dynamic -- resolved from `cody.json` \| Project output folder. Read from `cody.json > cody-product-builder > projectPath`. Default: `cody-projects/product-builder`. Resolved on activation and cached for the session. Re-resolved on `:cody refresh`. \|
27	\| {{cfPlanPhase}} \| `{{cfProject}}/plan` \| Plan phase folder. \|
28	\| {{cfWorkPhase}} \| `{{cfProject}}/build` \| Build phase folder. \|
29	\| {{cfReleaseNotes}} \| Dynamic -- resolved from `cody.json` \| Release notes folder. Read from `cody.json > cody-product-builder > releaseNotesPath`. If `"{{projectPath}}"`: resolves to `{{cfWorkPhase}}`. If `"{{projectRoot}}"`: resolves to project root. Otherwise: resolves to the custom path. Resolved on activation and cached for the session. Re-resolved on `:cody refresh`. \|
30	\| {{cfPrototypes}} \| `{{cfProject}}/prototypes` \| Prototype output folder. Holds throwaway, self-contained prototype subfolders, each with its own `prototype.md` and code. Sits outside the Plan and Build phases. \|
31	\| {{cfBestPractices}} \| `{{cfProject}}/best-practices` \| Project best-practices folder. Holds `project-best-practices.md`, the project's living record of build learnings. A project-level folder alongside the Plan and Build phases. \|
32
33	## File System Checks
34	- Always use the placeholder paths (e.g., `{{cfPlanPhase}}`, `{{cfProject}}`) when checking for files or folders. Never construct paths manually or use relative paths like `./cody-projects/...`.
35	- Before concluding that a folder is empty or files don't exist, always verify with at least two different methods (e.g., a glob search AND a directory listing). Never make decisions based on a single failed search. This prevents false negatives caused by path resolution issues.
36
37	## Executing Commands
38
39	- If the USER types any of the commands listed below, read and execute the corresponding command file.
40	- Only read command files when they are invoked. Do not pre-load all commands.
41
42	> ### `:cody help`
43	[AGENT TODO: Read and execute {{cfCommands}}/help.md]
44
45	> ### `:cody plan`
46	[AGENT TODO: Read and execute {{cfCommands}}/plan.md]
47
48	> ### `:cody build`
49	[AGENT TODO: Read and execute {{cfCommands}}/build.md]
50
51	> ### `:cody idea`
52	[AGENT TODO: Read and execute {{cfCommands}}/idea.md]
53
54	> ### `:cody prototype`
55	[AGENT TODO: Read and execute {{cfCommands}}/prototype.md]
56
57	> ### `:cody refresh`
58	[AGENT TODO: Read and execute {{cfCommands}}/refresh.md]
59
60	## Activation
61
62	When this skill is activated, AGENT, please execute the following exactly:
63
64	1. Resolve the project configuration. Resolving placeholder

People who liked this also viewed

6 picks

Type

cody-product-builder

65stars9forks

View on GitHub

How to install cody-product-builder?

ibuildwith-ai/cody-product-builder/cody-product-builder

$npx -y skills add ibuildwith-ai/cody-product-builder --skill cody-product-builder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Cody Product Builder
2
3	## Agent Instructions
4	- Read this entire document (`SKILL.md`) and commit it to memory.
5	- Make sure you check this document often if you need to understand how to process any Cody Product Builder commands.
6	- Anything that has [AGENT TODO: to do item] means you need to take action.
7	- When you see AGENT ANNOUNCE, anything in between the ```[message]``` (tick marks), you will display to the user exactly as stated.
8	- After every phase, make sure you re-read this document.
9	- {{cfPlaceholders}} used in commands are defined in this document, under the "Template Placeholder Values" section. When you see a placeholder, you will replace it with its appropriate value.
10	- The roles are as follows:
11	- USER Is the human guiding you in the building process.
12	- AGENT That's you! The AI Development AGENT.
13	- For detailed phase descriptions, document references, and version naming conventions, see `{{cfReferences}}/phases.md`.
14
15	## Template Placeholder Values
16	These placeholders are a pointer to actual values. They are created here and used throughout various commands. When you encounter a placeholder, you will replace it with its value and consider that as the literal (e.g. `{{cfCommands}}/help.md` translates to `commands/help.md`).
17
18	The skill-file placeholders (`{{cfRoot}}`, `{{cfAssets}}`, `{{cfCommands}}`, `{{cfReferences}}`) are paths relative to this skill's own folder.
19
20	\| Placeholder \| Maps to \| Description \|
21	\|------------\|---------\|-------------\|
22	\| {{cfRoot}} \| . \| This skill's root folder. \|
23	\| {{cfAssets}} \| assets \| Cody assets folder (templates and other static resources). \|
24	\| {{cfCommands}} \| commands \| Cody commands to be executed. \|
25	\| {{cfReferences}} \| references \| Shared reference content loaded on demand by commands. \|
26	\| {{cfProject}} \| Dynamic -- resolved from `cody.json` \| Project output folder. Read from `cody.json > cody-product-builder > projectPath`. Default: `cody-projects/product-builder`. Resolved on activation and cached for the session. Re-resolved on `:cody refresh`. \|
27	\| {{cfPlanPhase}} \| `{{cfProject}}/plan` \| Plan phase folder. \|
28	\| {{cfWorkPhase}} \| `{{cfProject}}/build` \| Build phase folder. \|
29	\| {{cfReleaseNotes}} \| Dynamic -- resolved from `cody.json` \| Release notes folder. Read from `cody.json > cody-product-builder > releaseNotesPath`. If `"{{projectPath}}"`: resolves to `{{cfWorkPhase}}`. If `"{{projectRoot}}"`: resolves to project root. Otherwise: resolves to the custom path. Resolved on activation and cached for the session. Re-resolved on `:cody refresh`. \|
30	\| {{cfPrototypes}} \| `{{cfProject}}/prototypes` \| Prototype output folder. Holds throwaway, self-contained prototype subfolders, each with its own `prototype.md` and code. Sits outside the Plan and Build phases. \|
31	\| {{cfBestPractices}} \| `{{cfProject}}/best-practices` \| Project best-practices folder. Holds `project-best-practices.md`, the project's living record of build learnings. A project-level folder alongside the Plan and Build phases. \|
32
33	## File System Checks
34	- Always use the placeholder paths (e.g., `{{cfPlanPhase}}`, `{{cfProject}}`) when checking for files or folders. Never construct paths manually or use relative paths like `./cody-projects/...`.
35	- Before concluding that a folder is empty or files don't exist, always verify with at least two different methods (e.g., a glob search AND a directory listing). Never make decisions based on a single failed search. This prevents false negatives caused by path resolution issues.
36
37	## Executing Commands
38
39	- If the USER types any of the commands listed below, read and execute the corresponding command file.
40	- Only read command files when they are invoked. Do not pre-load all commands.
41
42	> ### `:cody help`
43	[AGENT TODO: Read and execute {{cfCommands}}/help.md]
44
45	> ### `:cody plan`
46	[AGENT TODO: Read and execute {{cfCommands}}/plan.md]
47
48	> ### `:cody build`
49	[AGENT TODO: Read and execute {{cfCommands}}/build.md]
50
51	> ### `:cody idea`
52	[AGENT TODO: Read and execute {{cfCommands}}/idea.md]
53
54	> ### `:cody prototype`
55	[AGENT TODO: Read and execute {{cfCommands}}/prototype.md]
56
57	> ### `:cody refresh`
58	[AGENT TODO: Read and execute {{cfCommands}}/refresh.md]
59
60	## Activation
61
62	When this skill is activated, AGENT, please execute the following exactly:
63
64	1. Resolve the project configuration. Resolving placeholder

People who liked this also viewed

6 picks

Type