RFC 0016 drafted from alignment dialogue achieving 95% convergence: - Three-tier model: Identity (fixed) / Workflow (session) / Reference (on-demand) - Manifest-driven injection via .blue/context.manifest.yaml - URI addressing: blue://docs/, blue://context/, blue://state/ - Hooks push URIs, MCP resolves content - Progressive visibility: blue context show New ADRs ported from coherence-mcp: - 0014: Alignment Dialogue Agents (renamed from 0006) - 0015: Plausibility - 0016: You Know Who You Are Knowledge injection system: - hooks/session-start for SessionStart injection - knowledge/*.md files for global context - Expert pools with domain-specific relevance tiers - Updated /alignment-play skill with full scoring Spikes completed: - Context injection mechanisms (7 mechanisms designed) - ADR porting inventory (17 Blue ADRs mapped) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Creating Project Workflows
When a user asks to set up workflow, or blue_status indicates .blue/workflow.md is missing, help them create one.
Step 1: Analyze the Project
Look for:
- Build system:
Cargo.toml(Rust),package.json(Node),pyproject.toml(Python),go.mod(Go) - Existing branches: Check
git branch -afor patterns - CI config:
.github/workflows/,.gitlab-ci.yml,Jenkinsfile - Test setup: How are tests run? What coverage is expected?
- Existing docs:
CONTRIBUTING.md,README.mddevelopment sections
Step 2: Ask Clarifying Questions
Use AskUserQuestion to gather:
-
Branching strategy
- Trunk-based (main only)
- Feature branches off main
- Gitflow (develop, release branches)
-
RFC conventions
- Where do RFCs live? (
.blue/docs/rfcs/is default) - Naming pattern? (
NNNN-title.mdis default) - Approval process?
- Where do RFCs live? (
-
Pre-commit requirements
- Run tests?
- Lint checks?
- Type checking?
-
CI/CD expectations
- What must pass before merge?
- Deployment process?
Step 3: Generate workflow.md
Use the Write tool to create .blue/workflow.md:
# Project Workflow
## Branching Strategy
{Based on user answers}
## Development Flow
1. Create RFC via `blue_rfc_create`
2. Create worktree via `blue_worktree_create`
3. Implement in isolation
4. {Pre-commit checks}
5. Create PR via `blue_pr_create`
## Pre-Commit Checklist
- [ ] {test command}
- [ ] {lint command}
- [ ] {type check if applicable}
## RFC Conventions
- Location: `.blue/docs/rfcs/`
- Format: `NNNN-title.md`
- {Additional conventions}
## CI Requirements
{What must pass before merge}
Step 4: Confirm and Refine
After creating, ask:
- "I've created
.blue/workflow.md. Take a look and let me know if anything needs adjustment."
Example Conversation
User: "Help me set up the workflow for this project"
Claude:
- Reads project structure (Cargo.toml found → Rust project)
- Checks existing CI (.github/workflows/ci.yml found)
- Asks: "I see this is a Rust project with GitHub Actions. A few questions..."
- Generates workflow.md based on answers
- "Created
.blue/workflow.md. This will be injected into future sessions automatically."