feat(P03): multi-project support, NFR milestone versioning, phase context reset, install scripts (v0.3.0)
This commit is contained in:
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before challenging, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=30` for recent decisions and project history
|
||||
|
||||
@@ -19,6 +19,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before reviewing, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=10` for recent changes
|
||||
|
||||
@@ -20,6 +20,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before debugging, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for recent changes that may have caused the bug
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before verifying, load context from git first:
|
||||
|
||||
1. Run `git diff HEAD~10` to see recent code changes
|
||||
|
||||
@@ -20,6 +20,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before writing, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for recent changes that affect docs
|
||||
|
||||
@@ -20,6 +20,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before executing, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for recent project history
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before ideating, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=50` for full project history
|
||||
|
||||
@@ -22,6 +22,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before any operation, load project context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` and `git branch -a` to discover project structure
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before researching, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=50` for full project history
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before checking, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for recent decisions affecting this phase
|
||||
|
||||
@@ -19,6 +19,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before planning, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=50` to see recent decisions and project history
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before researching, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for any prior project history
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before synthesizing, load context from git first:
|
||||
|
||||
1. Run `git log --grep="research" --max-count=20` for prior research commits
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before researching, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=50` for project history and prior research
|
||||
|
||||
@@ -19,6 +19,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before roadmapping, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=30` for project history
|
||||
|
||||
@@ -20,6 +20,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before auditing, load context from git first:
|
||||
|
||||
1. Run `git log --grep="security" --max-count=20` for prior security decisions
|
||||
|
||||
@@ -19,6 +19,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before analyzing, load context from git first:
|
||||
|
||||
1. Run `git log --max-count=20` for recent problem-solving history
|
||||
|
||||
@@ -18,6 +18,13 @@ If the prompt contains a `<files_to_read>` block, you MUST use the Read tool to
|
||||
</role>
|
||||
|
||||
<project_context>
|
||||
If .ci/config.json has projects[] with length > 0, you are in multi-project mode.
|
||||
- Read active_project from .ci/config.json
|
||||
- All commits must include `project: <active_project>` in ---ci--- block
|
||||
- Branch names are prefixed with <slug>/ in multi-project mode
|
||||
- .ci/ files are in .ci/<slug>/ subdirectories
|
||||
If single-project mode (projects[] empty or absent), use existing conventions.
|
||||
|
||||
Before verifying, load context from git first:
|
||||
|
||||
1. Run `git log --grep="P##" --max-count=50` for all phase commits
|
||||
|
||||
Reference in New Issue
Block a user