Santhosh Janardhanan
f87ccccc4d
address each point.
**Changes Summary**
This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.
**Summary of Changes**
1. **Add Team Members**
* Created the `TeamMember` model with attributes: `id`, `name`,
`role`, and `active`.
* Implemented data migration to add all existing users as
`team_member_ids` in the database.
2. **Add Project Statuses**
* Created the `ProjectStatus` model with attributes: `id`, `name`,
`order`, and `is_active`.
* Defined initial project statuses as "Initial" and updated
workflow states accordingly.
3. **Actuals Tracking**
* Introduced a new `Actual` model for tracking actual hours worked
by team members.
* Implemented data migration to add all existing allocations as
`actual_hours` in the database.
* Added methods for updating and deleting actual records.
**Open Issues**
1. **Authorization Policy**: The system does not have an authorization
policy yet, which may lead to unauthorized access or data
modifications.
2. **Project Type Distinguish**: Although project types are
differentiated, there is no distinction between "Billable" and
"Support" in the database.
3. **Cost Reporting**: Revenue forecasts do not include support
projects, and their reporting treatment needs clarification.
**Implementation Roadmap**
1. **Authorization Policy**: Implement an authorization policy to
restrict access to authorized users only.
2. **Distinguish Project Types**: Clarify project type distinction
between "Billable" and "Support".
3. **Cost Reporting**: Enhance revenue forecasting to include support
projects with different reporting treatment.
**Task Assignments**
1. **Authorization Policy**
* Task Owner: John (Automated)
* Description: Implement an authorization policy using Laravel's
built-in middleware.
* Deadline: 2026-03-25
2. **Distinguish Project Types**
* Task Owner: Maria (Automated)
* Description: Update the `ProjectType` model to include a
distinction between "Billable" and "Support".
* Deadline: 2026-04-01
3. **Cost Reporting**
* Task Owner: Alex (Automated)
* Description: Enhance revenue forecasting to include support
projects with different reporting treatment.
* Deadline: 2026-04-15
153 lines
4.4 KiB
Markdown
153 lines
4.4 KiB
Markdown
---
|
|
name: "OPSX: Apply"
|
|
description: Implement tasks from an OpenSpec change (Experimental)
|
|
category: Workflow
|
|
tags: [workflow, artifacts, experimental]
|
|
---
|
|
|
|
Implement tasks from an OpenSpec change.
|
|
|
|
**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
|
|
|
|
**Steps**
|
|
|
|
1. **Select the change**
|
|
|
|
If a name is provided, use it. Otherwise:
|
|
- Infer from conversation context if the user mentioned a change
|
|
- Auto-select if only one active change exists
|
|
- If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
|
|
|
|
Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
|
|
|
|
2. **Check status to understand the schema**
|
|
```bash
|
|
openspec status --change "<name>" --json
|
|
```
|
|
Parse the JSON to understand:
|
|
- `schemaName`: The workflow being used (e.g., "spec-driven")
|
|
- Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
|
|
|
|
3. **Get apply instructions**
|
|
|
|
```bash
|
|
openspec instructions apply --change "<name>" --json
|
|
```
|
|
|
|
This returns:
|
|
- Context file paths (varies by schema)
|
|
- Progress (total, complete, remaining)
|
|
- Task list with status
|
|
- Dynamic instruction based on current state
|
|
|
|
**Handle states:**
|
|
- If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
|
|
- If `state: "all_done"`: congratulate, suggest archive
|
|
- Otherwise: proceed to implementation
|
|
|
|
4. **Read context files**
|
|
|
|
Read the files listed in `contextFiles` from the apply instructions output.
|
|
The files depend on the schema being used:
|
|
- **spec-driven**: proposal, specs, design, tasks
|
|
- Other schemas: follow the contextFiles from CLI output
|
|
|
|
5. **Show current progress**
|
|
|
|
Display:
|
|
- Schema being used
|
|
- Progress: "N/M tasks complete"
|
|
- Remaining tasks overview
|
|
- Dynamic instruction from CLI
|
|
|
|
6. **Implement tasks (loop until done or blocked)**
|
|
|
|
For each pending task:
|
|
- Show which task is being worked on
|
|
- Make the code changes required
|
|
- Keep changes minimal and focused
|
|
- Mark task complete in the tasks file: `- [ ]` → `- [x]`
|
|
- Continue to next task
|
|
|
|
**Pause if:**
|
|
- Task is unclear → ask for clarification
|
|
- Implementation reveals a design issue → suggest updating artifacts
|
|
- Error or blocker encountered → report and wait for guidance
|
|
- User interrupts
|
|
|
|
7. **On completion or pause, show status**
|
|
|
|
Display:
|
|
- Tasks completed this session
|
|
- Overall progress: "N/M tasks complete"
|
|
- If all done: suggest archive
|
|
- If paused: explain why and wait for guidance
|
|
|
|
**Output During Implementation**
|
|
|
|
```
|
|
## Implementing: <change-name> (schema: <schema-name>)
|
|
|
|
Working on task 3/7: <task description>
|
|
[...implementation happening...]
|
|
✓ Task complete
|
|
|
|
Working on task 4/7: <task description>
|
|
[...implementation happening...]
|
|
✓ Task complete
|
|
```
|
|
|
|
**Output On Completion**
|
|
|
|
```
|
|
## Implementation Complete
|
|
|
|
**Change:** <change-name>
|
|
**Schema:** <schema-name>
|
|
**Progress:** 7/7 tasks complete ✓
|
|
|
|
### Completed This Session
|
|
- [x] Task 1
|
|
- [x] Task 2
|
|
...
|
|
|
|
All tasks complete! You can archive this change with `/opsx:archive`.
|
|
```
|
|
|
|
**Output On Pause (Issue Encountered)**
|
|
|
|
```
|
|
## Implementation Paused
|
|
|
|
**Change:** <change-name>
|
|
**Schema:** <schema-name>
|
|
**Progress:** 4/7 tasks complete
|
|
|
|
### Issue Encountered
|
|
<description of the issue>
|
|
|
|
**Options:**
|
|
1. <option 1>
|
|
2. <option 2>
|
|
3. Other approach
|
|
|
|
What would you like to do?
|
|
```
|
|
|
|
**Guardrails**
|
|
- Keep going through tasks until done or blocked
|
|
- Always read context files before starting (from the apply instructions output)
|
|
- If task is ambiguous, pause and ask before implementing
|
|
- If implementation reveals issues, pause and suggest artifact updates
|
|
- Keep code changes minimal and scoped to each task
|
|
- Update task checkbox immediately after completing each task
|
|
- Pause on errors, blockers, or unclear requirements - don't guess
|
|
- Use contextFiles from CLI output, don't assume specific file names
|
|
|
|
**Fluid Workflow Integration**
|
|
|
|
This skill supports the "actions on a change" model:
|
|
|
|
- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
|
|
- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
|