@pixelfactoryio/theway 0.14.0 → 0.14.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/plugin/.claude-plugin/plugin.json +1 -1
- package/plugin/commands/archive.md +2 -2
- package/plugin/commands/document.md +2 -2
- package/plugin/commands/engineering.md +2 -2
- package/plugin/commands/list.md +2 -2
- package/plugin/commands/workflow.md +2 -2
- package/plugin/home/standards/commits.md +1 -1
- package/plugin/home/standards/develop.md +1 -1
- package/plugin/home/standards/git-host.md +1 -1
- package/plugin/home/standards/interaction.md +3 -3
- package/plugin/home/standards/spec-investigation.md +1 -1
- package/plugin/home/standards/spec-review.md +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "theway",
|
|
3
|
-
"version": "0.14.
|
|
3
|
+
"version": "0.14.1",
|
|
4
4
|
"description": "theway writes a spec and a numbered task list before any code, then implements the tasks in your session or through agents that open a reviewed, CI-green pull request.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Amine",
|
|
@@ -4,13 +4,13 @@ author: Amine
|
|
|
4
4
|
allowed-tools: Bash(theway:*)
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
#
|
|
7
|
+
# theway: Archive Spec
|
|
8
8
|
|
|
9
9
|
Archive a completed spec by moving it to the archive folder with a timestamp.
|
|
10
10
|
|
|
11
11
|
## Locate the home
|
|
12
12
|
|
|
13
|
-
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere:
|
|
13
|
+
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere: theway files of the current project are stored in `<home>/projects/<key>/`: run `theway project` for its key and folder; never compute the key yourself.
|
|
14
14
|
- If `theway` is not found, tell the user to add the folder theway is installed in (`~/.local/bin` by default) to their `PATH`, or to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins`, and stop.
|
|
15
15
|
- If any `theway` subcommand fails with `error: unknown command '<name>'`, the installed `theway` is older than these commands: tell the user to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins` and stop.
|
|
16
16
|
- If a `theway` subcommand exits 1 otherwise, quote the error line it wrote to stderr and stop, unless the step that runs it says what to do instead. The steps that do are `validate-id` (fix the ID), `next-id` (fix the series ID) and `archive` (open tasks, `--force` on explicit acceptance). Not every error line starts with `theway:`: `validate-id` and `next-id` write `invalid change id '…'` and `archive` writes `Error: …`.
|
|
@@ -4,13 +4,13 @@ author: Amine
|
|
|
4
4
|
allowed-tools: Bash(theway:*)
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
#
|
|
7
|
+
# theway: Document Mode
|
|
8
8
|
|
|
9
9
|
**IMPORTANT:** Keep documentation practical and actionable, not verbose. Use code examples over explanations.
|
|
10
10
|
|
|
11
11
|
## Locate the home
|
|
12
12
|
|
|
13
|
-
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere:
|
|
13
|
+
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere: theway files of the current project are stored in `<home>/projects/<key>/`: run `theway project` for its key and folder; never compute the key yourself.
|
|
14
14
|
- If `theway` is not found, tell the user to add the folder theway is installed in (`~/.local/bin` by default) to their `PATH`, or to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins`, and stop.
|
|
15
15
|
- If any `theway` subcommand fails with `error: unknown command '<name>'`, the installed `theway` is older than these commands: tell the user to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins` and stop.
|
|
16
16
|
- If a `theway` subcommand exits 1 otherwise, quote the error line it wrote to stderr and stop, unless the step that runs it says what to do instead. The steps that do are `validate-id` (fix the ID), `next-id` (fix the series ID) and `archive` (open tasks, `--force` on explicit acceptance). Not every error line starts with `theway:`: `validate-id` and `next-id` write `invalid change id '…'` and `archive` writes `Error: …`.
|
|
@@ -4,7 +4,7 @@ author: Amine
|
|
|
4
4
|
allowed-tools: Bash(theway:*)
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
#
|
|
7
|
+
# theway: Engineering
|
|
8
8
|
|
|
9
9
|
> **What this command produces.** A spec someone else can implement without guessing: the problem, what you found out, the decisions and why, and the tasks. With `--light`, a short spec: the problem, the evidence, the change file by file, and 1 to 3 tasks. The code is written later, by `/theway:workflow`, from that spec.
|
|
10
10
|
>
|
|
@@ -14,7 +14,7 @@ allowed-tools: Bash(theway:*)
|
|
|
14
14
|
|
|
15
15
|
## Locate the home
|
|
16
16
|
|
|
17
|
-
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere:
|
|
17
|
+
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere: theway files of the current project are stored in `<home>/projects/<key>/`: run `theway project` for its key and folder; never compute the key yourself.
|
|
18
18
|
- If `theway` is not found, tell the user to add the folder theway is installed in (`~/.local/bin` by default) to their `PATH`, or to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins`, and stop.
|
|
19
19
|
- If any `theway` subcommand fails with `error: unknown command '<name>'`, the installed `theway` is older than these commands: tell the user to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins` and stop.
|
|
20
20
|
- If a `theway` subcommand exits 1 otherwise, quote the error line it wrote to stderr and stop, unless the step that runs it says what to do instead. The steps that do are `validate-id` (fix the ID), `next-id` (fix the series ID) and `archive` (open tasks, `--force` on explicit acceptance). Not every error line starts with `theway:`: `validate-id` and `next-id` write `invalid change id '…'` and `archive` writes `Error: …`.
|
package/plugin/commands/list.md
CHANGED
|
@@ -4,11 +4,11 @@ author: Amine
|
|
|
4
4
|
allowed-tools: Bash(theway:*)
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
#
|
|
7
|
+
# theway: List Changes
|
|
8
8
|
|
|
9
9
|
## Locate the home
|
|
10
10
|
|
|
11
|
-
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere:
|
|
11
|
+
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere: theway files of the current project are stored in `<home>/projects/<key>/`: run `theway project` for its key and folder; never compute the key yourself.
|
|
12
12
|
- If `theway` is not found, tell the user to add the folder theway is installed in (`~/.local/bin` by default) to their `PATH`, or to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins`, and stop.
|
|
13
13
|
- If any `theway` subcommand fails with `error: unknown command '<name>'`, the installed `theway` is older than these commands: tell the user to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins` and stop.
|
|
14
14
|
- If a `theway` subcommand exits 1 otherwise, quote the error line it wrote to stderr and stop, unless the step that runs it says what to do instead. The steps that do are `validate-id` (fix the ID), `next-id` (fix the series ID) and `archive` (open tasks, `--force` on explicit acceptance). Not every error line starts with `theway:`: `validate-id` and `next-id` write `invalid change id '…'` and `archive` writes `Error: …`.
|
|
@@ -4,13 +4,13 @@ author: Amine
|
|
|
4
4
|
allowed-tools: Bash(theway:*)
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
#
|
|
7
|
+
# theway: Workflow
|
|
8
8
|
|
|
9
9
|
Run each change through one workflow: an ordered list of steps (`implement`, `review`, `agent`, `pr`) that `theway workflow` resolves from `<home>/projects/<key>/workflows/` or `<home>/workflows/`. The default workflow, the shipped `develop`, runs one `implement` step inline, in this session; steps with `agents: true` run through agents in the plugin workflow `theway:run-pipeline`, and steps with `agents: false` run inline.
|
|
10
10
|
|
|
11
11
|
## Locate the home
|
|
12
12
|
|
|
13
|
-
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere:
|
|
13
|
+
Run `theway path` and use the folder it prints as `<home>`, never a path from elsewhere: theway files of the current project are stored in `<home>/projects/<key>/`: run `theway project` for its key and folder; never compute the key yourself.
|
|
14
14
|
- If `theway` is not found, tell the user to add the folder theway is installed in (`~/.local/bin` by default) to their `PATH`, or to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins`, and stop.
|
|
15
15
|
- If any `theway` subcommand fails with `error: unknown command '<name>'`, the installed `theway` is older than these commands: tell the user to run `npx --yes @pixelfactoryio/theway@latest install` then `/reload-plugins` and stop.
|
|
16
16
|
- If a `theway` subcommand exits 1 otherwise, quote the error line it wrote to stderr and stop, unless the step that runs it says what to do instead. The steps that do are `validate-id` (fix the ID), `next-id` (fix the series ID) and `archive` (open tasks, `--force` on explicit acceptance). Not every error line starts with `theway:`: `validate-id` and `next-id` write `invalid change id '…'` and `archive` writes `Error: …`.
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# theway Commits
|
|
2
2
|
|
|
3
3
|
How a change's branch, commits and PR are named: `/theway:workflow` and its agents follow this whenever they create the feature branch, commit or open the PR. Edit it, or replace it for one project with `<home>/projects/<key>/standards/commits.md`, to use your team's conventions.
|
|
4
4
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# theway Git Host
|
|
2
2
|
|
|
3
3
|
The commands `/theway:workflow` and its agents run for each git host operation, here for GitHub through the `gh` CLI. Edit it, or replace it for one project with `<home>/projects/<key>/standards/git-host.md`, to use another host: keep the headings, which the command and its agents name, and change the commands under them.
|
|
4
4
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
#
|
|
1
|
+
# theway Interaction Conventions
|
|
2
2
|
|
|
3
|
-
Cross-cutting behavior for all
|
|
3
|
+
Cross-cutting behavior for all theway commands. Load and apply these in every mode.
|
|
4
4
|
|
|
5
5
|
## Exploration
|
|
6
6
|
|
|
@@ -9,7 +9,7 @@ Cross-cutting behavior for all TheWay commands. Load and apply these in every mo
|
|
|
9
9
|
|
|
10
10
|
## Reporting
|
|
11
11
|
|
|
12
|
-
- Never narrate
|
|
12
|
+
- Never narrate theway mode or which command to run next (e.g. "staying read-only", "no repo files touched", "run /theway:workflow to implement"), unless the command tells you to name one. Staying in the current mode is the default, not news.
|
|
13
13
|
- Report only spec/tasks/implementation progress and what is actionable.
|
|
14
14
|
|
|
15
15
|
## Authority
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# theway Spec Investigation
|
|
2
2
|
|
|
3
3
|
How a change is investigated before its spec is drafted: `/theway:engineering` follows this in its Investigate step, with or without `--light`. The command says what happens to a question this cannot settle, and which section of the spec the findings and the reproduction go to.
|
|
4
4
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# theway Spec Review
|
|
2
2
|
|
|
3
3
|
How a change's spec is reviewed before it is reported ready: `/theway:engineering` follows this, with or without `--light`. The command sets how many rounds run, which lenses run, and what a confirmed `decision` finding means.
|
|
4
4
|
|