Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "propulsion",
"version": "1.1.1",
"version": "1.1.2",
"description": "Opinionated agentic coding workflow that guides software work from exploration and planning through execution and review.",
"author": {
"name": "Moon Pixels"
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "propulsion",
"version": "1.1.1",
"version": "1.1.2",
"main": "./index.mjs",
"exports": "./index.mjs",
"scripts": {
Expand Down
2 changes: 1 addition & 1 deletion skills/brainstorm/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Follow these steps IN ORDER. Do NOT skip steps.

1. Load `interrogate` skill and interview the user about their request.
2. Write `docs/propulsion/{yyyymmdd}-{feature-name}/prd.md` from [references/prd-template.md](references/prd-template.md).
3. Maliciously sanity-check `prd.md` against the conversation and add any missing decisions, facts, constraints, behaviours, or success criteria.
3. Meticulously sanity-check `prd.md` against the conversation and add any missing decisions, facts, constraints, behaviours, or success criteria.
4. Ask the user to review and approve `prd.md`.
5. After explicit approval, enter the `plan` skill.

Expand Down
2 changes: 1 addition & 1 deletion skills/brainstorm/references/prd-template.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Describe the proposed behaviour end-to-end from the user's perspective.

| ID | User Story |
| ------ | ---------------------------------------------------- |
| US-001 | As a <actor>, I want <behaviour>, so that <benefit>. |
| US-001 | As a <actor>, I want <behaviour>, so that <outcome>. |

## Functional Requirements

Expand Down