zhongwei/gh-elct9620-claudekit-plugins-spec
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:25:19 +08:00
commit 92ace25b48
19 changed files with 1219 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
commands/architecture.md Normal file
View File

@@ -0,0 +1,38 @@
---
allowed-tools: Glob, Grep, Read, LS, TodoWrite
description: Draft architecture document or create architecture decision records (ADRs) to document significant architecture decisions.
argument-hint: [brief description of architecture decision]
---
# Rule
The `<execute>ARGUMENTS</execute>` will execute the main procedure.
# Role
You are a expert architect to clarify and document the architecture and design decisions of a software project.
# Context
Current Time: !`date +"%Y-%m-%d %H:%M:%S %Z"`
# Definition
<procedure name="main">
<description>Draft architecture document or create architecture decision records (ADRs) to document significant architecture decisions.</description>
<parameters name="description" optional="true">brief description of architecture decision to document</parameters>
<step>1. identity existing architecture document at docs/ARCHITECTURE.md</step>
<step>2. active spec-scaffold skill to get manual for architecture documentation</step>
<condition if="architecture document does not exist">
<step>3. use `cp` command to copy architecture template from `./templates/architecture.md` to `docs/ARCHITECTURE.md`</step>
<step>4. create initial ADR to document technology stack choices and codebase structure</step>
<return>path to the created architecture document</return>
</condition>
<step>5. follow the manual to draft a new ADR for the architecture decision based on the given {description}</step>
<step>6. review the ADR for completeness and clarity</step>
<return>path to the created ADR document</return>
</procedure>
# Task
<execute name="main">$ARGUMENTS</execute>

38
commands/clarify.md Normal file
View File

@@ -0,0 +1,38 @@
---
allowed-tools: Glob, Grep, Read, LS, TodoWrite
description: Update existing specification document to clarify user requirements.
argument-hint: feature_name, [clarification_details]
---
# Rule
The `<execute>ARGUMENTS</execute>` will execute the main procedure.
# Role
You are a product owner to clarify and update existing specification document to meet user requirements.
# Context
Current Time: !`date +"%Y-%m-%d %H:%M:%S %Z"`
# Definition
<procedure name="main">
<description>Update existing specification document to clarify user requirements.</description>
<parameters name="feature_name">feature_name to clarify in the specification document</parameters>
<parameters name="clarification_details" optional="true">clarification details to include in the specification document</parameters>
<step>1. identity existing specification document</step>
<step>3. active spec-scaffold skill to get manual for specification clarification</step>
<step>4. follow the manual to create the specification document based on the given {feature_name} and {clarification_details}</step>
<step>5. review the specification document for completeness and clarity</step>
<step>6. according to the manual to update roadmap & glossary</step>
<condition if="glossary conflicts found">
<step>7. use glossary document as highest priority to resolve conflicts</step>
</condition>
<return>path to the updated specification document</return>
</procedure>
# Task
<execute name="main">$ARGUMENTS</execute>

31
commands/constitution.md Normal file
View File

@@ -0,0 +1,31 @@
---
allowed-tools: Glob, Grep, Read, LS, TodoWrite
description: Create a project constitution for spec-central development and governance
---
# Rule
The `<execute>ARGUMENTS</execute>` will execute the main procedure.
# Role
You are a project manager to create a project constitution for spec-central development and governance.
# Context
Current Time: !`date +"%Y-%m-%d %H:%M:%S %Z"`
# Definition
<procedure name="main">
<description>Create or update the project constitution document</description>
<parameters name="principles">An optional brief principles to apply to this project constitution</parameters>
<step>1. active spec-scaffold skill to get manual for constitution creation</step>
<step>2. follow the manual to create or update the constitution document</step>
<step>3. review the constitution document for completeness and clarity</step>
<return>Path to the created or updated constitution document</return>
</procedure>
# Task
<execute name="main">$ARGUMENTS</execute>

41
commands/draft.md Normal file
View File

@@ -0,0 +1,41 @@
---
allowed-tools: Glob, Grep, Read, LS, TodoWrite
description: Draft a new specification document as single of truth for feature development.
argument-hint: one line brief user requirement to deliver value
---
# Rule
The `<execute>ARGUMENTS</execute>` will execute the main procedure.
# Role
You are a product owner to draft a new specification document as single of truth for feature development.
# Context
Current Time: !`date +"%Y-%m-%d %H:%M:%S %Z"`
# Definition
<procedure name="main">
<description>Draft a new specification document as single of truth for feature development.</description>
<parameters name="requirement">one line brief user requirement to deliver value</parameters>
<step>1. identity existing specification document or need to create a new one</step>
<condition if="existing specification document found">
<step>2. confirm with user to expend existing specification or create a new one use AskUserQuestion tool</step>
<return>use `/spec:clarify` command to update existing specification document</return>
</condition>
<step>3. active spec-scaffold skill to get manual for specification creation</step>
<step>4. follow the manual to create the specification document based on the given {requirement}</step>
<step>5. review the specification document for completeness and clarity</step>
<step>6. according to the manual to update roadmap & glossary</step>
<condition if="glossary conflicts found">
<step>7. use glossary document as highest priority to resolve conflicts</step>
</condition>
<return>path to the created specification document</return>
</procedure>
# Task
<execute name="main">$ARGUMENTS</execute>