Lightweight 4-gate pre-dev workflow for small features (<2 days)
Executes lightweight 4-gate pre-development workflow for small features under 2 days.
/plugin marketplace add lerianstudio/ring/plugin install ring-pm-team@ring[feature-name]I'm running the Small Track pre-development workflow (4 gates) for your feature.
This track is for features that:
If any of the above are false, use /pre-dev-full instead.
All artifacts will be saved to: docs/pre-dev/<feature-name>/
First, let me ask you about your feature:
Use the AskUserQuestion tool to gather:
Question 1: "What is the name of your feature?"
Question 2 (CONDITIONAL): "Does this feature require authentication or authorization?"
go.mod contains github.com/LerianStudio/lib-auth
golang.md → Access Manager Integration section during TRD creation (Gate 2)Question 3 (CONDITIONAL): "Is this a licensed product/plugin?"
go.mod contains github.com/LerianStudio/lib-license-go
golang.md → License Manager Integration section during TRD creation (Gate 2)Why auto-detection? Access Manager and License Manager are project-level infrastructure decisions, not feature-level. Once integrated, all features in the project inherit them.
After getting the feature name (and auth/license requirements if applicable), create the directory structure and run the 4-gate workflow:
mkdir -p docs/pre-dev/<feature-name>
Skill: pre-dev-research
Even small features benefit from quick research:
docs/pre-dev/<feature-name>/research.mdGate 0 Pass Criteria (Small Track):
Note: For very simple changes, Gate 0 can be abbreviated - focus on checking for existing patterns.
Skill: pre-dev-prd-creation
docs/pre-dev/<feature-name>/prd.mdGate 1 Pass Criteria:
Skill: pre-dev-trd-creation
docs/pre-dev/<feature-name>/prd.mddocs/pre-dev/<feature-name>/trd.mdGate 2 Pass Criteria:
Skill: pre-dev-task-breakdown
docs/pre-dev/<feature-name>/prd.mddocs/pre-dev/<feature-name>/trd.mddocs/pre-dev/<feature-name>/tasks.mdGate 3 Pass Criteria:
Report to human:
✅ Small Track (4 gates) complete for <feature-name>
Artifacts created:
- docs/pre-dev/<feature-name>/research.md (Gate 0) ← NEW
- docs/pre-dev/<feature-name>/prd.md (Gate 1)
- docs/pre-dev/<feature-name>/trd.md (Gate 2)
- docs/pre-dev/<feature-name>/tasks.md (Gate 3)
Skipped from full workflow:
- Feature Map (features simple enough to map directly)
- API Design (no new APIs)
- Data Model (no new data structures)
- Dependency Map (no new dependencies)
- Subtask Creation (tasks small enough already)
Next steps:
1. Review artifacts in docs/pre-dev/<feature-name>/
2. Use /worktree to create isolated workspace
3. Use /write-plan to create implementation plan
4. Execute the plan
/pre-dev-fulldocs/pre-dev/<feature-name>/This command orchestrates multiple skills in a 4-gate workflow.
| Gate | Skill | Purpose |
|---|---|---|
| 0 | pre-dev-research | Domain and technical research |
| 1 | pre-dev-prd-creation | Product requirements |
| 2 | pre-dev-trd-creation | Technical requirements |
| 3 | pre-dev-task-breakdown | Task decomposition |
For each gate:
Use Skill tool: [gate-skill]
Wait for human approval
Proceed to next gate
Each skill contains its own:
Do NOT skip gates. Each gate builds on the previous gate's output.